On 5 Jan, 13:03, Thomas Ferris Nicolaisen <[email protected]> wrote:
> Can you double check that the commit before is not failing as well, or
> maybe there are some other variables outside the test that are causing it
> to fail?
No the commit before is good. Even doing a "git bisect log" will list
it as good.
I'll just ended up parsing the output. Actually, the problem is not
the parsing, but keeping the output of the git bisect command since it
can potentially be very large. The parsing part can be quite simple:
sed -n s'/\([0-9a-f]\{40\}\) is the first bad commit/\1/p' $out
Alternatively I can do it manually, but git bisect run was so
simple....
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
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.
