From b9d9c5a27bea03802901872e0e056fb97b4c30a6 Mon Sep 17 00:00:00 2001 From: Jeremy Harris Date: Fri, 8 Apr 2016 19:37:13 +0100 Subject: 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. --- test/stderr/0476 | 1 + 1 file changed, 1 insertion(+) (limited to 'test/stderr/0476') diff --git a/test/stderr/0476 b/test/stderr/0476 index eaebb34d4..29b9c3ebb 100644 --- a/test/stderr/0476 +++ b/test/stderr/0476 @@ -36,6 +36,7 @@ transport_check_waiting entered sequence=1 local_max=500 global_max=-1 SMTP>> RSET H=127.0.0.1 [127.0.0.1] Remote host closed connection in response to RSET + SMTP(close)>> set_process_info: pppp delivering 10HmaX-0005vi-00: just tried 127.0.0.1 [127.0.0.1] for userx@test.ex: result OK Leaving t1 transport set_process_info: pppp delivering 10HmaX-0005vi-00 (just run t1 for userx@test.ex in subprocess) -- cgit v1.2.3