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

test/sealed-release.test.ts: "the way out: its fix released" is green on a loaded runner and rejoins the gate #1046

shipped production is serving it opened this has it
opened this

Pillar: P0 Trust (umbrella #586). The issue this waits on moves test/sealed-release.test.ts out of the gate because since 2026-10-11 the gate on main has been red on cases no pull touched, so nearly every pull's check failed on them. This issue owns bringing it back.

The case the way out: its fix released > a tag that does not contain the fix opens nothing failed unrelated pulls (#1023 for #423, #1015 for #872, #980 for #876).

Done means.

  • [ ] Find why the failing case goes red in the full gate run on a loaded machine and fix that cause. Widening a timeout alone is not a fix; waiting on the event the case reads is.
  • [ ] Move test/sealed-release.test.ts from EXCLUDED back to GATE in scripts/gate.ts in the same pull; test/check-list.test.ts stays green.
  • [ ] Run the file three times in a row with bun test test/sealed-release.test.ts and give the results in the pull.

Files. test/sealed-release.test.ts, scripts/gate.ts, and the source the cause is in.

commented

Dropped by the planner: test/sealed-release.test.ts is already in GATE in scripts/gate.ts at 2bdf6979 and main's gate is green with it; nothing left for this issue to do.

commented

Correction: the planner could not close this (it is assigned, and closing it is outside my scope). It is still open. The file is already in the gate, so a person can close it as dropped.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs