Testsuite: 0322 (pipelining errors) avoid triggering SIGPIPE
authorJeremy Harris <jgh146exb@wizmail.org>
Fri, 8 Apr 2016 18:37:13 +0000 (19:37 +0100)
committerJeremy Harris <jgh146exb@wizmail.org>
Fri, 8 Apr 2016 18:37:13 +0000 (19:37 +0100)
commitb9d9c5a27bea03802901872e0e056fb97b4c30a6
tree61e74b07329757389feafed4c34194a803f9174e
parentd223e9344978ee88ad04a231f00f7540d2b841e2
Testsuite: 0322 (pipelining errors) avoid triggering SIGPIPE

This was timing-dependent; if the exim closed the connection before
the script wrote to it _after_ triggerring an error, EPIPE/SIGPIPE.
Unexplained as yet: why runtest (perl) saw this as a 141 server
returncode (NB: 141-128 = 13 = SIGPIPE, the shell behaviour) when
"perldoc -v '$?'" (which runtest is coded to) says that a signum
should be in the top nibble of 16b.
18 files changed:
src/src/transports/smtp.c
test/runtest
test/scripts/0000-Basic/0322
test/src/server.c
test/stderr/0143
test/stderr/0217
test/stderr/0218
test/stderr/0276
test/stderr/0388
test/stderr/0467
test/stderr/0476
test/stderr/0525
test/stderr/2008
test/stderr/2013
test/stderr/2108
test/stderr/2113
test/stderr/3404
test/stdout/0322