[BUG] Timeout of 60000ms exceeded while running fixture "context" teardown.

Context:

• Playwright Version: 1.22
• Operating System: Manjaro Linux
• Node.js version: v16.15.0
• Browser: Chromium

When running my entire testsuite (currently 23 tests, 4 skipped, total duration 4 minutes, 7 spec files & workers), some tests fail with

[BUG] Timeout of 60000ms exceeded while running fixture "context" teardown.

But the issue doesn’t occur when running those tests individually (same as in https://github.com/microsoft/playwright/issues/14685, so maybe both issues have a shared cause), so it seems like there might be a performance issue with PW. Often the attachments are missing too when this issue occurs.

Since I can’t share the entire testsuite, I could maybe show someone in a call via screensharing if that helps. Or I could also share my Fixtures file but I’m not sure that’s what the error message is referring to.

[azad-derakhshani-GS]

@azad-derakhshani-GS were to able to solve this after discussing it privately? I’m getting the same timeout after I rerun recently passing tests.

Hey, yeah we had a call and from what I understand the timeout is also needed for the teardown, so if the timeout is too short (30s seems a bit short to me), it will fail even if the test itself passed, because there’s no time left for the teardown. Basically what @fobdy figured out too. 😃

I’m actually wondering if it’s worth creating a feature request to move PW’s automatic teardown out of that time window, since that’s not intuitive at all.
You’d think the automatic teardown would be separate from your tests, because you haven’t written the (automatic) teardown yourself, you’ve only written the tests and so you’d expect that’s what your specified timeout would exclusively apply to.

[fobdy]

Ah, ok got it. The issue was caused by general slowness of the test. So it took a bit more than 30S that’s why it was hard to clarify the root cause problem. Because deadline was at the time of “context” teardown.