Commit `1a32f2a7f4`

Techcable <techcable@techcable.net>

2022-08-22 13:38:03

test_runner: workaround #1923, isolating error traces in tests

Essentially #1923 means "caught" errors still show up in error return traces. The correct fix would require the compiler to fix this, but that could affect performance. For now, simply workaround this issue by clearing the return traces between tests. This means that "caught" errors in one test will not show up in the error traces of other tests.

master

1 parent 8667d6d

Changed files (1)

lib

test_runner.zig

@@ -96,6 +96,13 @@ pub fn main() void {
                 test_node.end();
             },
         }
+        // Workaround issue #1923 by clearing error stack traces between tests
+        //
+        // This is not a true fix, but helps isolate errors to the tests where they
+        // originate instead of confusing them all together
+        if (@errorReturnTrace()) |trace| {
+            trace.index = 0;
+        }
     }
     root_node.end();
     if (ok_count == test_fn_list.len) {

Commit 1a32f2a7f4

Commit `1a32f2a7f4`