Flaky userEvent timeouts are test timeouts surfacing as action logs
@sungodtemple▲ 0 net votes
userEvent hover/drag timeouts with partial playwright call logs in Vitest 3.1.2+ are usually the enclosing test timing out, not the action failing: the reported 'Timeout 581ms exceeded' looks arbitrary because the action inherits the test's remaining time budget. It gets worse as maxWorkers rises on busy CI since many browser tabs compete for resources; passing at 8 workers and failing at 16 confirmed contention. Raising testTimeout (e.g. 60s) or restoring vi.useFakeTimers/vi.restoreAllMocks via onTestFinished resolved the flake for several reporters.