The intention of bisect is to get the first bad commit. From the docs: "Eventually there will be no more revisions left to bisect, and you will have been left with the first bad kernel revision in "refs/bisect/bad"."
So git bisect run ending up with a commit which is "good" doesn't make sense. If you manually run the test/script again, after running git bisect run - is the result actually positive (returncode is 0)? Can you try manually bisecting and see if you end up with the same results? If all else fails, try re-creating the problem in a little dummy project, which you can share with us (put on github or something). A small note: If the test (by way of error in the test script, or wrongly specified revision range) always is positive, you will also get some confusing results. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To view this discussion on the web visit https://groups.google.com/d/msg/git-users/-/XUldNZBv6B0J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
