git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git bisect code 125 - "WFT?"

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 17, 2011, 17:56 UTC
Message-ID
<7vei654omv.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20110317072723.GH11931@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 5 quoted lines
>   2. If we do detect such a mishap, I'm not sure that "indeterminate
>      result" is necessarily the best result, as that will just keep
>      trying more and more commits without success. It is more likely a
>      sign of a poorly written test script, and the best thing we could
>      do is die and say "your test script looks buggy".

Exactly. I agree "Aborting the bisect as run-script is a crap" is the right thing to do here.

Previous: Jeff KingNext: Piotr Krukowiecki
Message 6 of 8 in “git bisect code 125 - "WFT?"”
  1. Piotr KrukowieckiMar 16, 2011
  2. Junio C HamanoMar 16, 2011
  3. Piotr KrukowieckiMar 16, 2011
  4. Johannes SixtMar 17, 2011
  5. Jeff KingMar 17, 2011
  6. Junio C HamanoMar 17, 2011
  7. 1/2 git bisect run: exit code 126 and 127 abort the runPiotr Krukowiecki, Mar 19, 2011
  8. 2/2 bisect documentation: exit codes 126,127 abort bisectPiotr Krukowiecki, Mar 19, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.