author | Jeff King <peff@peff.net> | |
Fri, 30 Jan 2009 08:21:01 +0000 (03:21 -0500) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Fri, 30 Jan 2009 09:14:26 +0000 (01:14 -0800) | ||
commit | 0ea8039644968e53d79a8dfbf739c87af4261d46 | |
tree | f69cf13d5e270fc96f73ca98c35a7e559ed990c0 | tree | snapshot |
parent | a3da8821208d6243dc5530d668f7c8f089814899 | commit | diff |
t0005: use SIGTERM for sigchain test
The signal tests consists of checking that each of our
handlers is executed, and that the test program was killed
by the final signal. We arbitrarily used SIGINT as the kill
signal.
However, some platforms (notably Solaris) will default
SIGINT to SIG_IGN if there is no controlling terminal. In
that case, we don't end up killing the program with the
final signal and the test fails.
This is a problem since the test script should not depend
on outside factors; let's use SIGTERM instead, which should
behave consistently.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
The signal tests consists of checking that each of our
handlers is executed, and that the test program was killed
by the final signal. We arbitrarily used SIGINT as the kill
signal.
However, some platforms (notably Solaris) will default
SIGINT to SIG_IGN if there is no controlling terminal. In
that case, we don't end up killing the program with the
final signal and the test fails.
This is a problem since the test script should not depend
on outside factors; let's use SIGTERM instead, which should
behave consistently.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
t/t0005-signals.sh | diff | blob | history | |
test-sigchain.c | diff | blob | history |