Fully automated bisecting with "git bisect run"

Posted Feb 8, 2009 16:06 UTC (Sun) by wfranzini (guest, #6946)
Parent article: Fully automated bisecting with "git bisect run"

I noticed only reading the article that 'git bisect' was unable to run the command being investigated.

People interested in a workflow that includes tests can look at Aegis (http://aegis.sf.net/). It also has an aebisect(1) command that run the command being investigated.

Fully automated bisecting with "git bisect run"

Posted Feb 10, 2009 4:41 UTC (Tue) by christian_couder (subscriber, #56350) [Link]

The long usage message is:

$ git bisect help
Usage: git bisect [help|start|bad|good|skip|next|reset|visualize|replay|log|run]

git bisect help
        print this long help message.
git bisect start [<bad> [<good>...]] [--] [<pathspec>...]
        reset bisect state and start bisection.
git bisect bad [<rev>]
        mark <rev> a known-bad revision.
git bisect good [<rev>...]
        mark <rev>... known-good revisions.
git bisect skip [(<rev>|<range>)...]
        mark <rev>... untestable revisions.
git bisect next
        find next bisection to test and check it out.
git bisect reset [<branch>]
        finish bisection search and go back to branch.
git bisect visualize
        show bisect status in gitk.
git bisect replay <logfile>
        replay bisection log.
git bisect log
        show bisect log.
git bisect run <cmd>...
        use <cmd>... to automatically bisect.

Please use "git help bisect" to get the full man page.

So you have to use "git bisect run <cmd>..." to automatically run the command you investigate. And if you don't want to automatically run the command, you can test by yourself at each step of the binary search and then use "git bisect good" or "git bisect bad" or "git bisect skip" depending on the result of your tests.