bisect usability trouble
Created originally on Bitbucket by benallard (Benoît Allard)
I liked the way bisect was integrated in the repository explorer in the old gtk version.
I also like the way it is now integrated it is really easy to use, actually, I could live with both, anyway, I've found a trouble with the new (2.0) way of using bisect:
Under some circumstances, the GUI thinks it is finished, even if mercurial reports that the investigations could continue. See the following message:
{{{ [command completed successfully Thu Mar 10 15:54:34 2011] % hg bisect --repository C:\InstallShield Projects\3.0\product-installer --bad . The first bad revision is: changeset: 461:71cf613ab3ac branch: x64 parent: 456:72d4e517c84e parent: 460:c65ed8fcd983 user: Benoit benoit@aeteurope.nl date: Thu Mar 10 14:15:42 2011 +0100 summary: merged
Not all ancestors of this changeset have been checked. To check the other ancestors, start from the common ancestor, 9e2f3c85e9df. [command completed successfully Thu Mar 10 15:54:39 2011] }}}
This is to reproduce with such a DAG:
{{{
o 9: bad
|
o 8: bad
|
| o 7: good
| |
o | 6
||
| o 5
| |
}}}
With as parameters for the dialog good: 7, bad: 9, 8 is proposed, diagnosed as bad, and here come the message and the wrong assumption from thg that the bisect is done. Mercurial, hints at testing 5.
I think thg should update to 5 and ask the result of the investigation.