From: Jeff King Date: Fri, 24 Jun 2016 19:45:04 +0000 (-0400) Subject: test_must_fail: use test_match_signal X-Git-Tag: v2.9.3~50^2~1 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=2472448c88ad72bd7d02d473590d2c17c2cd7424;p=thirdparty%2Fgit.git 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 Signed-off-by: Junio C Hamano --- 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