Uh oh!
There was an error while loading. Please reload this page.
fix: wrong stats when running with workers - #5215
Conversation
mirao
commented
Jan 23, 2026
@kobenguyent The test is running 2 suites in 3 browsers. 3.7.6 is slow 🐞, the test takes 2m15s (tested multiple times) 3.7.5 is fast ✔️ , the test takes 1m20s (tested multiple times) |
mirao
commented
Jan 26, 2026
It somehow depends on the specific test suites that are run. |
kobenguyent
commented
Jan 26, 2026
mirao
commented
Jan 26, 2026
@kobenguyent Good point! Definitely it's caused by #5386. If I comment out Can't reproduce in my test project (maybe I need to have some more test suites with various names...), but I'm able to reproduce it in my "production" project where many test suites already are. With test sorting, the parallelization per suite doesn't work and the test is slow 🐞 : Without test sorting the parallelization per suite works well and the test is fast ✔️ : |
mirao
commented
Jan 26, 2026
I created #5412 for the issue with parallelization per suite. It really doesn't belong to this PR. |
Motivation/Description of the PR
Applicable helpers:
Applicable plugins:
Type of change
Checklist:
npm run docs)npm run lint)npm test)