[PATCH 2/4] t0005: use test_match_signal as appropriate
- From
Jeff King <peff@peff.net>
- Date
- Jun 24, 2016, 19:44 UTC
- Message-ID
- <20160624194450.GB6441@sigill.intra.peff.net>
- In-Reply-To
- <20160624193924.GA6282@sigill.intra.peff.net>
The first test already uses this more portable construct (that was where it was factored from initially), but the later tests do a raw comparison against 141 to look for SIGPIPE, which can fail on some shells and platforms.
Signed-off-by: Jeff King <peff@peff.net> --- Again, I couldn't test these. They're skipped on MINGW, and ksh93 barfs before even executing the tests.
t/t0005-signals.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/t/t0005-signals.sh b/t/t0005-signals.sh index 2d96265..c80c995 100755 --- a/t/t0005-signals.sh +++ b/t/t0005-signals.sh @@ -36,12 +36,12 @@ test_expect_success 'create blob' ' test_expect_success !MINGW 'a constipated git dies with SIGPIPE' ' OUT=$( ((large_git; echo $? 1>&3) | :) 3>&1 ) && - test "$OUT" -eq 141 + test_match_signal 13 "$OUT" ' test_expect_success !MINGW 'a constipated git dies with SIGPIPE even if parent ignores it' ' OUT=$( ((trap "" PIPE; large_git; echo $? 1>&3) | :) 3>&1 ) && - test "$OUT" -eq 141 + test_match_signal 13 "$OUT" ' test_done
-- 2.9.0.215.gc5c4261