From: Johannes Sixt <j6t@kdbg.org>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: git@vger.kernel.org, 'Joachim Schmitz' <jojo@schmitz-digital.de>
Subject: Re: [BUG] test_must_fail: does not correctly detect failures - Was Git 2.16.0-rc2 Test Summary on NonStop
Date: Sun, 14 Jan 2018 19:40:43 +0100 [thread overview]
Message-ID: <59d3adab-4a95-4ef5-2d8f-ef4c7b797156@kdbg.org> (raw)
In-Reply-To: <001a01d38d57$d36c7d10$7a457730$@nexbridge.com>
Am 14.01.2018 um 17:50 schrieb Randall S. Becker:
> 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
next prev parent reply other threads:[~2018-01-14 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-13 20:16 [BUG] test_must_fail: does not correctly detect failures - Was Git 2.16.0-rc2 Test Summary on NonStop Randall S. Becker
2018-01-14 16:50 ` Randall S. Becker
2018-01-14 18:40 ` Johannes Sixt [this message]
2018-01-14 21:32 ` Randall S. Becker
2018-01-15 2:37 ` Randall S. Becker
2018-01-15 7:05 ` Johannes Sixt
2018-01-15 14:25 ` Randall S. Becker
2018-01-16 3:00 ` brian m. carlson
2018-01-16 3:31 ` Randall S. Becker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=59d3adab-4a95-4ef5-2d8f-ef4c7b797156@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@vger.kernel.org \
--cc=jojo@schmitz-digital.de \
--cc=rsbecker@nexbridge.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).