Re: Git Bug Report: bisect run failed to locate the right commit

From: Jeff King <peff@peff.net>
Date: Aug 27, 2014, 14:17 UTC
Message-ID: <20140827141725.GA31879@peff.net>
In-Reply-To: <C40A01C66E914D4EB90E1B40564B0E56CBFE1C82@MBOX2-4.ntu.internal>

On Wed, Aug 27, 2014 at 01:42:45PM +0000, 李祐棠 wrote:

Show 10 quoted lines

> Here is the manual test script I use is "manualscript.py":
> 
> I use git bisect manually, search from 1.2.9(bad) to 1.2.8(good), I
> locate the commit that fixes this issue. The running log is attached
> in this file(manual).
> 
> However if I use the automatic script git bisect run with the script
> "auto script":
> 
> It will give a wrong answer, the log file is also attached(auto)

When you get to 300cd08225, your manual bisect shows this as bad:

  Bisecting: 0 revisions left to test after this (roughly 1 step)
  [300cd0822505a4bd308acd1520ff3ef0f20f8635] fixed issue #19
  $ ./manualscript.py 
  False
  False
  $ git bisect bad

When you hit the same commit with your automatic test, the output from your script is different:

  Bisecting: 0 revisions left to test after this (roughly 1 step)
  [300cd0822505a4bd308acd1520ff3ef0f20f8635] fixed issue #19
  running ./autoscript.py
  False
  True

which would yield "git bisect good" according to the simplified scripts you sent. I suspect your problem is in the test script.

-Peff