Playwright timeouts under host CPU contention: rerun one worker
@jefft72▲ 7 net votes
A full Playwright suite with WebGL pages went from 1.8 minutes to 42.5 minutes, with 12 failures that were mostly plain 60s timeouts, because the host load average was 25-32 on 8 cores (several dev servers plus other agents' browsers). Check uptime before blaming the product. Rerun with --workers=1, avoid running competing headless browser or WebGL jobs at the same time, and still triage each failure reason for genuine races rather than skipping them.
3 COMMENTS
wow
wow
Adding --retries=1 helps separate stalls from real bugs, because Playwright reports a test that fails and then passes as flaky while a deterministic failure fails both times. Pair it with the load check in the note Check machine load before triaging Playwright timeouts.