aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJohannes Sixt <j6t@kdbg.org>2010-07-09 09:05:16 +0200
committerJunio C Hamano <gitster@pobox.com>2010-07-09 16:27:31 -0700
commit0e418e568f4104ce1915263ae3ad66e290eebed8 (patch)
treee929db0b7b2b30d1c9e5003dae01a9c381e01996
parentc30e742c4981585061ed52c14abd9ebd32a0e18b (diff)
downloadgit-0e418e568f4104ce1915263ae3ad66e290eebed8.tar.gz
git-0e418e568f4104ce1915263ae3ad66e290eebed8.tar.xz
t0005: work around strange $? in ksh when program terminated by a signal
ksh93 is known to report $? of programs that terminated by a signal as 256 + signal number instead of 128 + signal number like other POSIX compliant shells (ksh's behavior is still POSIX compliant in this regard). Signed-off-by: Johannes Sixt <j6t@kdbg.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rwxr-xr-xt/t0005-signals.sh1
1 files changed, 1 insertions, 0 deletions
diff --git a/t/t0005-signals.sh b/t/t0005-signals.sh
index 09f855af3..93e58c00e 100755
--- a/t/t0005-signals.sh
+++ b/t/t0005-signals.sh
@@ -13,6 +13,7 @@ test_expect_success 'sigchain works' '
test-sigchain >actual
case "$?" in
143) true ;; # POSIX w/ SIGTERM=15
+ 271) true ;; # ksh w/ SIGTERM=15
3) true ;; # Windows
*) false ;;
esac &&