From: Jeff King Date: Wed, 24 Feb 2016 07:45:49 GMT Subject: [PATCH 3/4] test_must_fail: report number of unexpected signal Message-ID: <20160224074548.GC9481@sigill.intra.peff.net> In-Reply-To: <20160224073603.GA9163@sigill.intra.peff.net> If a command is marked as test_must_fail but dies with a signal, we consider that a problem and report the error to stderr. However, we don't say _which_ signal; knowing that can make debugging easier. Let's share as much as we know. Signed-off-by: Jeff King --- Not necessary for the fix, obviously, but I implemented this while trying to figure out what in the world was going on with the write_or_die() thing. :) t/test-lib-functions.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/t/test-lib-functions.sh b/t/test-lib-functions.sh index c64e5a5..8d99eb3 100644 --- a/t/test-lib-functions.sh +++ b/t/test-lib-functions.sh @@ -617,7 +617,7 @@ test_must_fail () { return 0 elif test $exit_code -gt 129 && test $exit_code -le 192 then - echo >&2 "test_must_fail: died by signal: $*" + echo >&2 "test_must_fail: died by signal $(($exit_code - 128)): $*" return 1 elif test $exit_code -eq 127 then -- 2.7.2.645.g4e1306c