Comment 3 for bug 195134

On Sun, 2008-02-24 at 21:57 +0000, James Westby wrote:
>
> I think the check at each level would be heavyweight for
> some cases, for instance ./bzr selftest at each thread
> would just take too long, so I would prefer to do it at
> the top and then "bisect" if there was an error, however
> I can see the reasoning.

For upstream to merge each patch separately, they will want each patch
appropriately tested. If we can define an interface that lets that
happen (for instance, for bzr, running a selected subset of tests in
each thread), then we're aiding the user in getting their code accepted:
and thats really the point :)

> Mentioning that, is there a use case for loom-bisect or similar?
> I'll file another bug if you agree.

Hmm, I think someone should play and see how it fairs; it may be that
bisect is just fine as is, or that loom should extend bisect when it is
installed.

-Rob

--
GPG key available at: <http://www.robertcollins.net/keys.txt>.
>