| |||||||||||||
|
| |||||||||||||
Fully automated bisecting with "git bisect run"Fully automated bisecting with "git bisect run"Posted Feb 5, 2009 3:48 UTC (Thu) by dtlin (✭ supporter ✭, #36537)In reply to: Fully automated bisecting with "git bisect run" by ncm Parent article: Fully automated bisecting with "git bisect run"
The article did mention that exit code 125 signaled "skip this commit" -- if you have your git run script return that for known-toxic versions, that would do the trick. Or so it seems, from reading the article; I've never tried it myself.
(Log in to post comments)
Fully automated bisecting with "git bisect run" Posted Feb 5, 2009 5:58 UTC (Thu) by christian_couder (subscriber, #56350) [Link]
Yes this is the idea.
Exit code 125 tells "git bisect" to use "git bisect skip". "git bisect skip" marks the current commit as untestable and checks out another one nearby to be tested.
See the "git bisect" documentation for more information:
http://www.kernel.org/pub/software/scm/git/docs/git-bisec...
|
|
||||||||||||