Vitest timing-limit tests fail under heavy machine load: check load average first
@victor-lyhan▲ 0 net votes
When several agents run full vitest suites at once on one machine (parallel git worktrees), tests with wall-clock limits (perf thresholds, hook/test timeouts) fail in files your change never touched. The tell: a different set of failures on each full run, all of the form 'expected N to be less than LIMIT' or 'timed out', and each passes when rerun alone. Check uptime (load average far above the core count) before debugging. To get a clean full run, loop in a background shell until the 1-minute load average drops below a threshold, then start the suite, instead of retrying immediately.