From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH] t0005: ksh93 portability workaround
Date: Tue, 31 May 2016 15:47:01 -0700 [thread overview]
Message-ID: <xmqqinxt3kwq.fsf@gitster.mtv.corp.google.com> (raw)
The test has two things ksh93 does not happy about:
* It thinks "(( command1; command2 ) | command3)" is a perfectly
sane way to write a pipeline. ksh93, unlike other POSIX shells,
does not like the two open parentheses next to each other for
whatever reason it has.
* It adds 256, unlike 128 that are used by other POSIX shells, to
the signal number that caused the process to die when coming up
with the exit status.
What is interesting is that we knew about the latter issue and had a
workaround in the test-sigchain test when verifying that SIGTERM
works OK, but we didn't have corresponding workaround for SIGPIPE.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
t/t0005-signals.sh | 18 ++++++++++++++----
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git a/t/t0005-signals.sh b/t/t0005-signals.sh
index e7f27eb..12b4efb 100755
--- a/t/t0005-signals.sh
+++ b/t/t0005-signals.sh
@@ -9,6 +9,16 @@ two
one
EOF
+died_with_sigpipe () {
+ case "$1" in
+ 141 | 269)
+ # POSIX w/ SIGPIPE=13 gives 141
+ # ksh w/ SIGPIPE=13 gives 269
+ true ;;
+ *) false ;;
+ esac
+}
+
test_expect_success 'sigchain works' '
{ test-sigchain >actual; ret=$?; } &&
case "$ret" in
@@ -40,13 +50,13 @@ test_expect_success 'create blob' '
'
test_expect_success !MINGW 'a constipated git dies with SIGPIPE' '
- OUT=$( ((large_git; echo $? 1>&3) | :) 3>&1 ) &&
- test "$OUT" -eq 141
+ OUT=$( ( (large_git; echo $? 1>&3) | :) 3>&1 ) &&
+ died_with_sigpipe "$OUT"
'
test_expect_success !MINGW 'a constipated git dies with SIGPIPE even if parent ignores it' '
- OUT=$( ((trap "" PIPE; large_git; echo $? 1>&3) | :) 3>&1 ) &&
- test "$OUT" -eq 141
+ OUT=$( ( (trap "" PIPE; large_git; echo $? 1>&3) | :) 3>&1 ) &&
+ died_with_sigpipe "$OUT"
'
test_done
next reply other threads:[~2016-05-31 22:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 22:47 Junio C Hamano [this message]
2016-05-31 22:49 ` [PATCH] t0005: ksh93 portability workaround Eric Sunshine
2016-05-31 23:03 ` Jeff King
2016-05-31 23:17 ` Junio C Hamano
2016-05-31 23:04 ` [PATCH] t/lib-git-daemon: ksh " Junio C Hamano
2016-05-31 23:05 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqinxt3kwq.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.