I still think git show will show the commit that breaks the build.

Here's the output of me running bisect on a toy project, the target commit 
is 74a227:


First, a oneline log of my recent commits:

c5f7e3a8a943b5a3d2a1b43981730405f9b9f9a0 A random commit message: flanky
c6a92b9c359f0ae4332d63d2b6786fc85ffdd67e A random commit message: 
anamnestically
426f9b4d84d683d6cfa841550c76e356b86c48f1 A random commit message: rikk
74a277ba449d800d1346151228aa2dd05f7783b1 Break the build
8aa8ead6437ccf72c02a89d74347101f23d82945 A random commit message: pose
f50f1932a87bef2fc3c4964bfce6cab865febf8d A random commit message: 
procatarxis
3049456ee0687dcba375cefe31e2bebbfa974dca A random commit message: 
hidropoiesis
d5c745d307d6770c34dfd995b4cf77c725c622b2 A random commit message: farmtown
d4cf807a21d2c9de45513ee81154040fedcb4597 A random commit message: inviolate

I start bisecting the range, just like above:

➜  ~/projects/agnes/[master]>git bisect start HEAD 
d4cf807a21d2c9de45513ee81154040fedcb4597             
 tfnico@Thomas-Ferris-Nicolaisens-iMac [14:31:41]
Bisecting: 3 revisions left to test after this (roughly 2 steps)
[8aa8ead6437ccf72c02a89d74347101f23d82945] A random commit message: pose
➜  ~/projects/agnes/[(8aa8ead...)|BISECTING]>git bisect run mvn clean test

[.... lots of output ...]


This is the final result at the end of the output:

74a277ba449d800d1346151228aa2dd05f7783b1 is the first bad commit
commit 74a277ba449d800d1346151228aa2dd05f7783b1
Author: Thomas Ferris Nicolaisen <thomas.nicolai...@company.com>
Date:   Thu Jan 5 12:47:45 2012 +0100

    Break the build

:040000 040000 cfcbef1c6b45c4a93f2863be81a6ecbe780eeaab 
0c2c45d3e7369ba609508f807c2b1d849fb3cefc M src
bisect run success

Now, run git show:

➜  ~/projects/agnes/[(broke-the-build)|BISECTING]>git show                 
                              tfnico@Thomas-Ferris-Nicolaisens-iMac 
[14:32:35]
commit 74a277ba449d800d1346151228aa2dd05f7783b1
Author: Thomas Ferris Nicolaisen <thomas.nicolai...@company.com>
Date:   Thu Jan 5 12:47:45 2012 +0100

    Break the build
[.... diff ...]

As it stands, it works as described. Here's the bisect log for show:

➜  ~/projects/agnes/[(broke-the-build)|BISECTING]>git bisect log           
                              tfnico@Thomas-Ferris-Nicolaisens-iMac 
[14:32:52]
# bad: [c5f7e3a8a943b5a3d2a1b43981730405f9b9f9a0] A random commit message: 
flanky
# good: [d4cf807a21d2c9de45513ee81154040fedcb4597] A random commit message: 
inviolate
git bisect start 'HEAD' 'd4cf807a21d2c9de45513ee81154040fedcb4597'
# good: [8aa8ead6437ccf72c02a89d74347101f23d82945] A random commit message: 
pose
git bisect good 8aa8ead6437ccf72c02a89d74347101f23d82945
# bad: [426f9b4d84d683d6cfa841550c76e356b86c48f1] A random commit message: 
rikk
git bisect bad 426f9b4d84d683d6cfa841550c76e356b86c48f1
# bad: [74a277ba449d800d1346151228aa2dd05f7783b1] Break the build
git bisect bad 74a277ba449d800d1346151228aa2dd05f7783b1

I still believe that there's something fishy going on in your test.. Care 
to share some concrete examples?

-- 
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/-/lJA9km9kXqMJ.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Reply via email to