From: Johannes Sixt Date: Sun, 14 Jan 2018 18:40:43 GMT Subject: Re: [BUG] test_must_fail: does not correctly detect failures - Was Git 2.16.0-rc2 Test Summary on NonStop 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: > 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