{"thread":{"id":"1838","subject":"[PATCH] bisect succeeds but has non zero exit code","startedAt":"2005-09-17T04:32:39Z","lastAt":"2005-09-17T04:32:39Z","messageCount":1,"participants":["Anton Blanchard"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"8748","messageId":"20050917043239.GG14962@krispykreme","threadId":"1838","inReplyTo":null,"subject":"[PATCH] bisect succeeds but has non zero exit code","fromName":"Anton Blanchard","fromEmail":"anton@samba.org","sentAt":"2005-09-17T04:32:39Z","receivedAt":"2005-09-17T04:32:39Z","isPatch":true,"sender":{"key":"anton@samba.org","avatar":null},"body":"\nHi,\n\nI was writing some scripts to automate a bisection search and noticed\nI could get a non zero exit code when the command succeeded:\n\n# git-bisect start\n# echo $?\n0\n\n# git-bisect good ef4cbee0b0d0f791bb593f99b702410f3c0efce6\n# echo $?\n1\n\n# git bisect bad 6d36ba629e0ef47a03d3703ee1d38143c25532a8\nBisecting: 13 revisions left to test after this\n[1619cca2921f6927f4240e03f413d4165c7002fc] Partially revert \"Fix time\ngoing twice as fast problem on ATI Xpress chipsets\"\n# echo $?\n0\n\nIt looks like bisect_next_check returns false and we return a non zero\nexit code. The following patch forces a good exit code in that case.\n\nSigned-off-by: Anton Blanchard <anton@samba.org>\n---\n\n--- git-bisect.sh.orig\t2005-09-15 17:37:08.000000000 +1000\n+++ git-bisect.sh\t2005-09-17 14:24:30.000000000 +1000\n@@ -111,6 +111,7 @@\n \n bisect_auto_next() {\n \tbisect_next_check && bisect_next\n+\ttrue\n }\n \n bisect_next() {\n"}]}