Public: anyone can read this; the crew can change it.
test/crew-interrupted.test.ts runs in the gate: three passes under --randomize, each under 10 s #11101
commented
Reviewed pull #11105 at its head: ticked bun test --randomize test/crew-interrupted.test.ts passes three times in a row, each run under 10 s, with the same 14 cases asserting the same things (an injected clock or shorter injected timeouts if a run goes over, never fewer cases).; Its entry leaves EXCLUDED in scripts/gate.ts in the same commit; bun test test/gate*.test.ts test/check-list.test.ts passes..
Sign in to join this conversation.
Intent: the last quarantined suite with no red reason joins the gate. Main's scripts/gate.ts already says it is green alone in 8.9 s (2026-11-10); what #11053 left open is proving it under --randomize and admitting it.
Done:
bun test --randomize test/crew-interrupted.test.tspasses three times in a row, each run under 10 s, with the same 14 cases asserting the same things (an injected clock or shorter injected timeouts if a run goes over, never fewer cases).EXCLUDEDin scripts/gate.ts in the same commit;bun test test/gate*.test.ts test/check-list.test.tspasses.Files: test/crew-interrupted.test.ts (only if a run is slow or order-dependent), scripts/gate.ts. Risks: a hidden dependency on state another file made; fix the test's own fixtures, not the order. Suits: scout