cc @targos

It still fails on my mac:

test at test/issue-3356.js:1:1
✖ test/issue-3356.js (30003.947833ms)
  'test timed out after 30000ms'

I can try to debug a bit after lunch

It fails because the expected error doesn't happen (await response.text() resolves).

It works if I only increase the last timeout. I pushed some changes, but I don't know if the test is still valid that way.
My commit includes a refactoring to remove the use of tspl so that it doesn't wait for 30 seconds before failing the test in case there's a mismatch between assertions and plan.

There's something wrong with the test, I think. Even with 2 seconds, it fails (less often, but still)

Is it possible that the issue is not timing-related, but due to another test that has some unintended side-effect?

Note that the timeout before the try/catch can be removed and the test will still pass if run in isolation.

Then let's remove that.

Timing tests are flaky by nature unfortunately :(. We can 100% skip this in CITGM and other envs.