Summary
test/audit-fixes.test.ts > TimeoutError carries the configured timeout has been intermittently failing across multiple test-coverage cycles (5, 6, 7). It passes in isolation and on most full-suite runs, but fails roughly 1 in N times when the suite is under load.
Notes
Suggested fix
- Inspect the test for an assertion that compares an observed elapsed time against the configured
timeoutMs. Either widen the tolerance or pin the timeout via vi.useFakeTimers().
- Alternatively, add a retry annotation (
it.retry(2)) if the underlying behavior is correct and only the timing is flaky.
Filed during cycle 7 hedge-coverage review (PR #119).
Summary
test/audit-fixes.test.ts > TimeoutError carries the configured timeouthas been intermittently failing across multiple test-coverage cycles (5, 6, 7). It passes in isolation and on most full-suite runs, but fails roughly 1 in N times when the suite is under load.Notes
pnpm testruns, not when the file is run alone.timeoutMswindow may be undersized relative to the host's scheduling jitter when the test runner is saturated.Suggested fix
timeoutMs. Either widen the tolerance or pin the timeout viavi.useFakeTimers().it.retry(2)) if the underlying behavior is correct and only the timing is flaky.Filed during cycle 7 hedge-coverage review (PR #119).