jedarden/pdftract
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix(marathon): forbid ad-hoc bare cargo test, mandate nextest filters

Browse source 
A bare `cargo test --package pdftract-core --lib buffer` hung and stalled the
marathon ~5h on 2026-05-25, bypassing the nextest terminate-after guard. The
instruction only banned bare cargo test at the final gate, not for narrow/iterative
runs — which is exactly where the trap is.

instruction.md: extend the ban to narrow/iterative runs and document the nextest
filter equivalents (-E 'test(...)', -p <crate> <filter>).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
jedarden 2026-05-25 19:45:42 -04:00
parent 90d1b9a83d
commit 9628a2b77c
1 changed files with 10 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
.marathon/instruction.md
View file

@ -81,9 +81,18 @@ bf claim <bead-id> --model claude-code-glm-4.7 --harness needle --harness-versio
cargo clippy --all-targets -- -D warnings cargo clippy --all-targets -- -D warnings
cargo fmt cargo fmt
cargo nextest run # NEVER bare `cargo test` — see CLAUDE.md "Test hygiene". cargo nextest run # NEVER bare `cargo test` — see CLAUDE.md "Test hygiene".
# nextest kills hung tests via .config/nextest.toml slow-timeout. # nextest kills hung tests via .config/nextest.toml terminate-after.
# If nextest is unavailable: timeout --kill-after=30s 600s cargo test --all-targets # If nextest is unavailable: timeout --kill-after=30s 600s cargo test --all-targets
``` ```
**This ban covers narrow / iterative runs too** — to exercise a single test or package,
filter *through nextest*; never run a bare `cargo test -p … --lib …`:
```bash
cargo nextest run -E 'test(buffer)' # by test-name substring
cargo nextest run -p pdftract-core buffer # by package + filter
```
(On 2026-05-25 a bare `cargo test --package pdftract-core --lib buffer` hung and stalled
the loop ~5h — it bypassed the nextest timeout. Ad-hoc runs are exactly where the guard
matters; a "quick check" with bare `cargo test` is the trap.)
If the run is killed by a timeout (nextest `TIMEOUT`/`TERMINATED`, or `timeout` exit 124), If the run is killed by a timeout (nextest `TIMEOUT`/`TERMINATED`, or `timeout` exit 124),
a test hung — fix it; never close the bead claiming the tests passed. a test hung — fix it; never close the bead claiming the tests passed.