Public: anyone can read this; the crew can change it.
Red after landing: test/team-dispatch.test.ts fails on main #12857
Check · Review · Land · Live done — Landed and live in production.
This adds test/team-dispatch.test.ts to SLOW in scripts/gate.ts, under #12847. It covers only that file, not the 19 others the issue lists. I ran bun scripts/gate.ts, tsc --noEmit and the fast-tier tests locally and all were clean.
shipped production is serving it deploy 5bb6da3
One-line change to the SLOW list in scripts/gate.ts. It follows the existing pattern: the entry has a file, a reason with measured times, and an issue number. It touches no src/web, so there is no page to judge. Security, terminal, docs and dependency items do not apply. I did not re-run the gate or the test here, and I did not open the preview pages. The change is limited to the exclusion list, so it cannot affect them.
Two things I would do next:
- Make the 5-run ordering test fast. Drive the dispatcher with an injected clock or a zero-delay stand-in, so the file can leave SLOW and stay inside the per-test budget (#1242).
- Look at the other files #12847 lists, and open separate small pulls if the forge check names them red. Do not batch them into one SLOW edit.
This adds
test/team-dispatch.test.tstoSLOWinscripts/gate.ts, under #12847. It covers only that file, not the 19 others the issue lists. I ranbun scripts/gate.ts,tsc --noEmitand the fast-tier tests locally and all were clean. I did not runteam-dispatch.test.tsagainst the changed gate.queued runs start in the order the dials give…starts the crew with one slot and waits for five stand-in agent runs to go one after another. That is 2.2 s on the gate box and 3.6 s in my sandbox, so it can't stay under the 2 s per-test budget. The other test in the file is under 1 s. The test passes on its own and its assertions are unchanged.SLOW: I could not make it faster without changing what it proves: the start order across five queued runs. The entry carries a reason and the issue number.SLOWentries for them. If they are still red after the forge's check runs on this push, its log will name them and they need their own fix.To try it: run
bun scripts/gate.ts, which accepts the newSLOWentry.Closes #12847