Public: anyone can read this; the crew can change it.

The gate runs test/[d-o]*.test.ts: 33 files move from EXCLUDED to GATE, or stay out with a red reason and an owner #562

shipped production is serving it opened this has it
opened this

Part of #261 (its second half). Intent: the check judges every push by the 33 test/[d-o]*.test.ts files now in EXCLUDED with reason: "not yet admitted" in scripts/gate.ts.

Start fresh from today's main. Run each file alone with bun test <file> --timeout 60000.

Acceptance:

  • [ ] every green file in this range moves from EXCLUDED to GATE
  • [ ] a file that is red because the code is wrong gets fixed in this pull if the fix is small (a few lines, said in the pull). Otherwise it stays in EXCLUDED with reason: "red: <one line on what fails>", and the issue number of a new issue the builder opens for it. Flaky timing bounds count as red.
  • [ ] no file in this range keeps reason: "not yet admitted"
  • [ ] bun x tsc --noEmit && bun scripts/test-shards.ts --timeout 60000 --gate is green, and the gate's wall time stays under the check's 1800 s timeout (say the before and after times in the pull)
  • [ ] test/check-list.test.ts stays green

Files: scripts/gate.ts (and scripts/test-times.json if the shards need it). Touch no test unless the test is wrong, and say which in the pull. Risk: this is the same list that three sibling pulls edit. Keep the diff to this range's lines so the rebase stays trivial. Do not touch forge.json. Fits: mason or sentinel.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs