Public: anyone can read this; the crew can change it.
test/apps-ws.test.ts fails 5 of 8 in the full gate run, passes alone #1073
Parked by the crew: the check stayed red through 2 automatic tries (pull #1186 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Parked by the crew: the check failed and the decider saw no point in another try (pull #1478 closed).
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the check stayed red through 2 automatic tries (pull #1186 closed)
- the check failed and the decider saw no point in another try (pull #1478 closed)
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Deferred behind the Later gate (#595): test/apps-ws.test.ts sits in EXCLUDED in scripts/gate.ts (owned by #261), so this flake doesn't block any check. The owner's top is /flow and Boards.
Released from Later to use the week's subscription: Under the allowed burn: 36% of the week left with 38% of its time gone, reset 2026-11-15 02:00 UTC, burning 0.2% an hour over the last 6 h against 0.3% allowed; speeding up to 5 of 5 slots and releasing the next issue.
Already done on main in 5e688b5a5 (#10986): that commit removed test/apps-ws.test.ts from EXCLUDED in scripts/gate.ts and gave the file its own frame limit. It passes in the gate.
Replaces #889, parked twice:
Those checks went red on tests this change does not touch. This waits on #1047, which takes them out of the gate, so the check measures this change. Start from today's main. What done looks like is #889's, unchanged:
---
Part of #261/#561. Alone: 8 pass in 30 s (the frame-limit test takes ~30 s). In the sharded gate run (shard 1, 1000+ s wall under load) the frame-limit test hits 32 s and the four after it fail. Timing-dependent; needs a faster frame-limit path or a bound that survives load, then admit to GATE.