Confusing Mercurial history - was: Re: Hotspot segfaulting on Linux SPARC

[Roman Kennke]

Am 16.04.2018 um 20:17 schrieb John Paul Adrian Glaubitz:
> On 04/16/2018 05:07 PM, John Paul Adrian Glaubitz wrote:
>> I am trying to bisect the segefault I am seeing on linux-sparc.
> 
> So, I have tried dozens of revisions now and I can't find one that builds fine.
> This is becoming really frustrating, especially since the history with Mercurial
> seems completely random.
> 
> I would normally expect a changeset that was checked in in July to be included
> in a revision that was checked in in August. I don't understand how one is supposed
> to perform bi-secting with Mercurial if something as basic as a working history
> doesn't work in Mercurial.

You're probably wrongly assuming that commit history is linear. It is
not. TBH, I don't really know how hg bisect works with branchy history.
It usually works fairly well in my experience. It will probably get
confused if you start out with two revision on different branches? Or
are you trying to bisect manually?

Here's some information around this stuff:
http://hgbook.red-bean.com/read/finding-and-fixing-mistakes.html#sec:undo:bisect


Cheers, Roman