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

test/rehearsal-real.test.ts runs in the gate: its two real rolls stay green under the gate's load #11098

Closed opened this has it

Landed in pull #11114 · run

opened this

Intent: test/rehearsal-real.test.ts is green alone today (3 of 3 under bun test --randomize --timeout 60000, 2026-11-10, found on #11085) but was last red under the gate's load on main@accaa65 (#7632, closed): the second real roll's old forge did not come up. It stays in scripts/gate.ts EXCLUDED, under this issue, until it is proven under load.

Done:

Files: test/rehearsal-real.test.ts, scripts/gate.ts

2 earlier comments
commented

Reviewed pull #11114 at its head: ticked its EXCLUDED entry is deleted and the file's header stops citing #7632. left open: bun scripts/flake-hunt.ts admit test/rehearsal-real.test.ts is ten green on the check host, or the red run names what did not come up and that is fixed — The ten runs were in the builder's sandbox, not on the check host; the forge check is one green run there, not the ten-run admission..

commented

Left open after pull #11114 landed: 1 unticked item remains (bun scripts/flake-hunt.ts admit test/rehearsal-real.test.ts is ten green on the check host, or the red run names what did not come up and that is fixed). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.

commented

Split: the unticked box (flake-hunt admit ten green on the check host, or a red that names its cause and is fixed) is #11169.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs