On this same platform, there is also a test failure:
FAIL: tests/misc/seq-epipe
==========================
diff: code: No such file or directory
seq emitted incorrect error on EPIPE
seq: write error: Broken pipe
FAIL tests/misc/seq-epipe.sh (exit status: 1)
Here it's the command
timeout 10 sh -c 'trap "" PIPE && { seq inf 2>err; echo $? >code; } | head
-n1' >out
which does not always behave as expected:
$ for i in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19; do timeout 10 sh
-c 'rm -f code; trap "" PIPE && { seq inf 2>err; echo $? >code; } | head -n1'
>out; ls -l code; done
-rw-r--r-- 1 bruno staff 2 Mar 1 21:34 code
-rw-r--r-- 1 bruno staff 2 Mar 1 21:34 code
-rw-r--r-- 1 bruno staff 2 Mar 1 21:34 code
code: No such file or directory
code: No such file or directory
code: No such file or directory
code: No such file or directory
code: No such file or directory
code: No such file or directory
code: No such file or directory
code: No such file or directory
code: No such file or directory
code: No such file or directory
-rw-r--r-- 1 bruno staff 2 Mar 1 21:34 code
-rw-r--r-- 1 bruno staff 2 Mar 1 21:34 code
-rw-r--r-- 1 bruno staff 2 Mar 1 21:34 code
code: No such file or directory
code: No such file or directory
code: No such file or directory
code: No such file or directory
Whereas, again, with 'bash' instead of 'sh', it's all right.
Bruno
