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

Re: [BUG] test_must_fail: does not correctly detect failures - Was Git 2.16.0-rc2 Test Summary on NonStop

From
Johannes Sixt <j6t@kdbg.org>
Date
Jan 14, 2018, 18:40 UTC
Message-ID
<59d3adab-4a95-4ef5-2d8f-ef4c7b797156@kdbg.org>
In-Reply-To
<001a01d38d57$d36c7d10$7a457730$@nexbridge.com>
Am 14.01.2018 um 17:50 schrieb Randall S. Becker:
Show 6 quoted lines
> Follow-up: This looks like the completion code from perl on NonStop is not
> the same as expected by git in the case of failures. I need to debug this to
> get more details to the team. We have had completion issues before relating
> to interpretation problems between perl, bash, and git in this platform, so
> I'm assuming this to be likely again but need to track down the specifics.
> Can anyone point me to where the detection is within git or the execv?

Perhaps you are looking for wait_or_whine() in run-command.c? But this function cannot do anything if perl alread exits with an exotic code (> 128 even though no signal was received).

-- Hannes
Previous: Randall S. BeckerNext: Randall S. Becker
Message 3 of 9 in “[BUG] test_must_fail: does not correctly detect failures - Was Git 2.16.0-rc2 Test Summary on NonStop”
  1. Randall S. BeckerJan 13, 2018
  2. Randall S. BeckerJan 14, 2018
  3. Johannes SixtJan 14, 2018
  4. Randall S. BeckerJan 14, 2018
  5. Randall S. BeckerJan 15, 2018
  6. Johannes SixtJan 15, 2018
  7. Randall S. BeckerJan 15, 2018
  8. brian m. carlsonJan 16, 2018
  9. Randall S. BeckerJan 16, 2018

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.