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>
This commit is contained in:

committed by
Junio C Hamano

parent
c30e742c49
commit
0e418e568f
@ -13,6 +13,7 @@ test_expect_success 'sigchain works' '
|
|||||||
test-sigchain >actual
|
test-sigchain >actual
|
||||||
case "$?" in
|
case "$?" in
|
||||||
143) true ;; # POSIX w/ SIGTERM=15
|
143) true ;; # POSIX w/ SIGTERM=15
|
||||||
|
271) true ;; # ksh w/ SIGTERM=15
|
||||||
3) true ;; # Windows
|
3) true ;; # Windows
|
||||||
*) false ;;
|
*) false ;;
|
||||||
esac &&
|
esac &&
|
||||||
|
Reference in New Issue
Block a user