On 2010-04-06 09:24 , Olberd wrote:
> The process completed now.
>
> Branched 29 revision(s).
>
> And seems functional.
> rune@hilbert:~/test.bzr$ bzr check
> Checking working tree at '/home/rune/test.bzr/testallGB'.
> Checking branch at 'file:///home/rune/test.bzr/testallGB/'.
> Checking repository at 'file:///home/rune/test.bzr/'.
> checked repository <bzrlib.transport.local.LocalTransport url=file:///home/rune/test.bzr/> format <RepositoryFormat2a>
> 29 revisions
> 50188 file-ids
> checked branch file:///home/rune/test.bzr/testallGB/ format Branch format 6
>
> Could something be missing because of the "bzr: out of memory" error, or
> would that get caught by the check?
That is precisely the sort of thing that check checks. The above looks
like exactly right for the results of ``bzr check``.
On 2010-04-06 09:24 , Olberd wrote: ~/test. bzr$ bzr check rune/test. bzr/testallGB' . //home/ rune/test. bzr/testallGB/ '. //home/ rune/test. bzr/'. transport. local.LocalTran sport url=file: ///home/ rune/test. bzr/> format <RepositoryForm at2a> /home/rune/ test.bzr/ testallGB/ format Branch format 6
> The process completed now.
>
> Branched 29 revision(s).
>
> And seems functional.
> rune@hilbert:
> Checking working tree at '/home/
> Checking branch at 'file:/
> Checking repository at 'file:/
> checked repository <bzrlib.
> 29 revisions
> 50188 file-ids
> checked branch file://
>
> Could something be missing because of the "bzr: out of memory" error, or
> would that get caught by the check?
That is precisely the sort of thing that check checks. The above looks
like exactly right for the results of ``bzr check``.