Hi, On Wed, Aug 27, 2014 at 3:42 PM, 李祐棠 <r01942...@ntu.edu.tw> wrote: > Dear Git developers: > > I just found a suspicious bug that might cause by git-bisect run. > > Version: > The git version is 1.9.2, running on Archlinux 3.14.2 > > The step to produce the error: > Here is the repository I participate: > https://github.com/gawel/pyquery > > It got a issue #74, that gives a wrong result in version 1.2.8 > and this is fixed in 1.2.9 > > 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)
Your "manual" log contains: Bisecting: 0 revisions left to test after this (roughly 1 step) [300cd0822505a4bd308acd1520ff3ef0f20f8635] fixed issue #19 $ ./manualscript.py False False While your "auto" log contains: Bisecting: 0 revisions left to test after this (roughly 1 step) [300cd0822505a4bd308acd1520ff3ef0f20f8635] fixed issue #19 running ./autoscript.py False True So for the commit 300cd0822505a4bd308acd1520ff3ef0f20f8635 it looks like your manualscript.py and your autoscript.py don't return the same result. Could you check that by doing something like: $ git checkout -b testscripts 300cd0822505a4bd308acd1520ff3ef0f20f8635 $ ./manualscript.py $ echo "manualscript.py exit code: $?" $ ./autoscript.py $ echo "autoscript.py exit code: $?" ? By the way you can get a better bisect log by running "git bisect log" after your bisection. Best, Christian. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
