Skip to content

Commit 09bed52

Browse files
committed
test(server): the suite reports its flakes instead of retrying past them
Three separate causes were hiding behind one `retry: 2`, which is silent when it rescues a test, so seven weeks of reds turning green left no trace. - Eight cases in src/git/GitManager.test.ts carried their own 12s/20s deadlines as a bare positional argument to `it.effect`, inside the config's 120s. The file contains no literal "timeout", so grepping for the word finds nothing. - CodexCollabRuntime.integration.test.ts generated its script to a fixed path in `src/`, and the mock peer derives `.interrupts`/`.responses` from it. Two concurrent runs deleted each other's fixtures: 9 of 10 red before, 0 of 10 after. A killed run also left those files untracked inside `src/`. - The retry itself is gone. The stale checkpoint capture it was really covering for was fixed in 49bf064. Measured after all three: five green full server suite runs at `--retry=0`, three unloaded and two run as a concurrent pair -- the contention the old comment blamed. Gate: EXIT=0, 959 files, 10,085 passed, 8 skipped, 0 failed.
1 parent 49bf064 commit 09bed52

3 files changed

Lines changed: 350 additions & 358 deletions

File tree

0 commit comments

Comments
 (0)