From 2b019b1e3a01f0aa8794807d9c7e2a14df1e48b9 Mon Sep 17 00:00:00 2001 From: Jeremy Harris Date: Tue, 20 Dec 2022 20:31:58 +0000 Subject: Testsuite: avoid munge false-pos spotting a new PID --- test/runtest | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'test/runtest') diff --git a/test/runtest b/test/runtest index 3cc534c98..38e03b3ac 100755 --- a/test/runtest +++ b/test/runtest @@ -342,7 +342,7 @@ return @yield; # into the same standard values throughout the data from a single test. # Message ids get this treatment (can't be made reliable for times), and # times in dumped retry databases are also handled in a special way, as are -# incoming port numbers. +# incoming port numbers and PIDs. # On entry to the subroutine, the file to write to is already opened with the # name MUNGED. The input file name is the only argument to the subroutine. @@ -1077,7 +1077,7 @@ RESET_AFTER_EXTRA_LINE_READ: /x; # Lines with a leading pid - s/^(\d+)\s(?!(?:previous message|in\s))/new_value($1, "p%s", \$next_pid) . ' '/e; + s/^(\d+)\s(?!(?:previous message|in\s|bytes remain in))/new_value($1, "p%s", \$next_pid) . ' '/e; # Debugging lines for Exim terminations and process-generation -- cgit v1.2.3