Re: git bisect replay produces wrong result

From: Christian Couder <christian.couder@gmail.com>
Date: Aug 31, 2015, 07:54 UTC
Message-ID: <CAP8UFD2sAyQp6uUuBBdmGtU1+9heE14pivJs8n8a84UY22yJsQ@mail.gmail.com>
In-Reply-To: <8737z15r1d.fsf@notabene.neil.brown.name>

Hi,

On Sun, Aug 30, 2015 at 6:38 AM, Neil Brown <neil@brown.name> wrote:

Show 18 quoted lines

>
> Hi,
>  the following git-bisect log - applied to a recent linux-kernel tree
>  produced different end results when I use "git bisect replay"
>  and when I just run it as a shell script.
>
> $ git bisect replay /tmp/log
> We are not bisecting.
> Bisecting: a merge base must be tested
> [2decb2682f80759f631c8332f9a2a34a02150a03] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
>
>
> $ bash /tmp/log
> ....
> Bisecting: 2 revisions left to test after this (roughly 1 step)
> [57127645d79d2e83e801f141f7d03f64accf28aa] s390/zcrypt: Introduce new SHA-512 based Pseudo Random Generator.
>
> Is "git bisect replay" doing the wrong thing, or am I confused?

I think you are right and "git bisect replay" is buggy. "git bisect replay" should display the same thing. I will take a look at fixing this.

Thanks for the report, Christian.