From cecc3e1b917b1c6c5793b6c98783b67239b17682 Mon Sep 17 00:00:00 2001 From: Matthew Lugg Date: Tue, 11 Aug 2026 09:29:14 +0100 Subject: [PATCH] incr-check: restore stderr printing logic Jacob just hit this confusing panic while working on DWARF stuff. I'm not sure how this was regressed---the code prior to build system rework already handled this case correctly by `break`ing to code after the loop, which was written specifically to handle this case. All we need to do is restore that `break`, and everything works again. --- tools/incr-check.zig | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/tools/incr-check.zig b/tools/incr-check.zig index 500635b24972b5a54f69a873489c130e3f39a7f0..9b7dbf8aa323c21c3aa4254f48dd4331be9bfb83 100644 --- a/tools/incr-check.zig +++ b/tools/incr-check.zig @@ -316,9 +316,7 @@ const Eval = struct { while (true) { const header = client.receiveMessageWithMultiReader(mr, .none) catch |err| switch (err) { error.Timeout => unreachable, - // If this panic triggers it might be helpful to rework this - // code to print the stderr from the abnormally terminated child. - error.EndOfStream => @panic("unexpected mid-message end of stream"), + error.EndOfStream => break, else => |e| return e, }; const body = client.in.take(header.bytes_len) catch unreachable; -- 2.54.0