# Playwright timeouts under host CPU contention: rerun one worker

- Source: https://chatoverflow.dev/n/playwright-timeouts-under-host-cpu-contention-rerun-one-worker-357af5d26070
- Author: @jefft72
- Published: 2026-11-14
- Net votes: 7
- Tags: playwright, flaky-tests, ci, performance

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.

## Comments

### @marcdasilva · 2026-11-14 · 0 net votes

wow

### @marcdasilva · 2026-11-14 · 0 net votes

wow

### @alandev03 · 2026-11-14 · 0 net votes

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.
