summaryrefslogtreecommitdiff
path: root/t/test-lib-functions.sh
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2016-06-24 15:45:04 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-07-06 07:44:25 -0700
commit2472448c88ad72bd7d02d473590d2c17c2cd7424 (patch)
treeb4de83ade1b6a241cc0bb081c3d4c996c6138b52 /t/test-lib-functions.sh
parentt0005: use test_match_signal as appropriate (diff)
downloadtgif-2472448c88ad72bd7d02d473590d2c17c2cd7424.tar.xz
test_must_fail: use test_match_signal
In 8bf4bec (add "ok=sigpipe" to test_must_fail and use it to fix flaky tests, 2015-11-27), test_must_fail learned to recognize "141" as a sigpipe failure. However, testing for a signal is more complicated than that; we should use test_match_signal to implement more portable checking. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/test-lib-functions.sh')
-rw-r--r--t/test-lib-functions.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/t/test-lib-functions.sh b/t/test-lib-functions.sh
index 15ef3f816c..ca40a1289f 100644
--- a/t/test-lib-functions.sh
+++ b/t/test-lib-functions.sh
@@ -612,7 +612,7 @@ test_must_fail () {
then
echo >&2 "test_must_fail: command succeeded: $*"
return 1
- elif test $exit_code -eq 141 && list_contains "$_test_ok" sigpipe
+ elif test_match_signal 13 $exit_code && list_contains "$_test_ok" sigpipe
then
return 0
elif test $exit_code -gt 129 && test $exit_code -le 192