If anything this should improve the experience of bisecting, because you'll be able to bisect known-good csets on m-c and only at the end step in to the merge csets which may or may not be good.
Right now we say that when people push a patch queue to m-c every patch should be green, but in practice that's often not the case. Right now when you bisect you have no way that I'm aware of to say "bisect only the tips of pushes", because hg doesn't store that information, so you end up bisecting through many bad csets. On Wed, Apr 3, 2013 at 6:43 PM, Gary Kwong <gkw...@mozilla.com> wrote: >> Another potential problem with this approach is that we will have more >> merge changes in m-c, which generally screws with hg bisect. Personally >> I already have enough trouble with hg bisect to the point where I don't >> use it because I can't trust it. This may be a legitimate problem for >> some, but it's not for me. > > > autoBisect relies heavily on `hg bisect` and has been working well with > JSBugMon especially in Spidermonkey for the better part of ~ 4 years now. > > -Gary > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
