The full suite run can time out files that pass alone (an overloaded
shared host, a suite-wide deadline in the runner): MAINT-28 T307 was
judged on 30 TIMEOUTs, T325 on a file that passes alone in 230 s.
- With testFileCommand set, every file the full run reports as TIMEOUT
or FAIL (testIssuePattern, default ^(TIMEOUT|FAIL)\s+(\S+); lines are
read as the run streams) is rerun alone in the clone,
testRerunJobs at a time, testFileTimeoutSec each, at most
testRerunMax files.
- A file that still fails or times out alone runs again on the base,
in a git worktree next to the clone (<clone>-verifier-base), which is
removed and pruned afterwards. Without a worktree, base stays "not
run".
- The verifier gets a table (file, full run, alone on head, on base,
meaning) and is told: passes alone does not count; fails on base too
is not caused by the change; name every file it counts.
- Only file names of letters, digits and _ . - / reach the shell; no
".." parts, no leading "-".
- 12 new tests; each of the 23 new rules was also broken on purpose and
caught.
Version 0.4.9.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MdqPWvuDpbpRvDEdURoAwo