# test_runner: workaround \#1923, isolating error traces in tests · gitcafe/zig

[View on GitCafe](https://git.cafe/gitcafe/zig/commit/1a32f2a7f40328799537cc94240a57054a1275bc)

Repository: [gitcafe/zig](https://git.cafe/gitcafe/zig)

Visibility: public

Requested revision: 1a32f2a7f40328799537cc94240a57054a1275bc

Requested commit: 1a32f2a7f40328799537cc94240a57054a1275bc

Commit: 1a32f2a7f40328799537cc94240a57054a1275bc

Tree: 0bd21f4ede2338f4b7adeba20d0e16c1f739413a

Author: Techcable

Committer: GitHub

## Message

```
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.
```

## Parents

- [8667d6d61e8217159377c0e22bc35075848d1202](https://git.cafe/gitcafe/zig/commit/8667d6d61e8217159377c0e22bc35075848d1202?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zig/tree/1a32f2a7f40328799537cc94240a57054a1275bc?format=markdown)