New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: UI seems to lock on Windows making tests time out #30629
Comments
@pbrzosko I have played with your repro a bit. Things are slowing down indeed, but some of that is expected due to increased parallelization between single worker and many workers. However, I did not reach 10 seconds. UI mode is noticeably slower. I think this is due to trace being recorded by UI mode, and disk access slowing everything down. Perhaps the shared disk access may even slow down all workers in parallel, which looks like "locking effect". |
How about every worker using its own directory to gather trace and then everything is combined at the end of the run? |
Each worker has its own directory already.
I guess the filesystem is implemented differently? Note that it was just my first idea, and the problem might be entirely different.
Everything is ~1.8x slower in UI mode. Going up to 8 workers slows down each test ~2x.
That could easily be the case with the antivirus. You can check that by running with |
I will check the trace impact. But when we run with 1 worker in UI mode, times are as expected. So it seems like some locking issue which is only visible with many workers running. |
I'll close this issue, because there is no action item for Playwright right now. If you come up with some new findings, please file a new issue and link to this one, so we can continue the discussion. |
Yyy, say that again @dgozman? You have clear evodence that tests run over 10s instead of one and you say there is nothing to do from your side? |
Version
1.42.1
Steps to reproduce
Expected behavior
All tests should run similar amount of time and not time out. Here is a screenshot of them running on OSX:
Actual behavior
On Windows, it seems like tests are locking each other on some resource. Thus they start to time out and run very slowly:
Additional context
When run with one worker, it seems to work fine:
Environment
The text was updated successfully, but these errors were encountered: