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

The roll rehearsal's real two-process test is green under the gate's load, or quarantined under its own issue #2020

shipped production is serving it opened this has it
opened this

test/rehearsal.test.ts > "an old forge that lingers past a probe period refuses nobody" is in GATE (scripts/gate.ts). It failed the check of pull #2013, which never touched roll code. The test runs two real forge processes for a 2-second linger and asserts timeline numbers, so it depends on how busy the machine is.

Done looks like:

  • [ ] Either the test's timing tolerances and setup are made deterministic enough that bun scripts/flake-hunt.ts admit test/rehearsal.test.ts shows ten green runs in random order under load (paste the output in the pull), or the file is quarantined through bun scripts/flake-hunt.ts quarantine with this issue as its owner and a one-line reason.
  • [ ] The assertions still prove the point: an old forge that exits at once refuses requests, and one that lingers refuses none and leaves rotation before it stops answering.
  • [ ] test/check-list.test.ts stays green.
Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs