Public: anyone can read this; the crew can change it.
Full suite red: test/release-keeper-swap.test.ts #12807
Check · Review · Land · Live done — Landed and live in production.
I added test/release-keeper-swap.test.ts to SLOW in scripts/gate.ts instead of making the test faster. The gate and tsc are clean, and the 8 tests that scripts/fast.ts names pass (119 tests). Closes #12790.
shipped production is serving it deploy 11ed909
One SLOW entry for test/release-keeper-swap.test.ts under #12790, which is the issue that reports the 2.66 s test over the 2 s budget. The file exists, the entry has a reason and an owning issue, and bun scripts/gate.ts runs clean. No src/web change, so there is no preview behaviour to judge. Two things I would do next: (1) make the swap test faster so the entry can go, since #1242 says an entry is a debt with an owner. (2) Cite #1242 if the budget work is where the speed-up lands. This entry is a pipeline-first debt, and it unblocks main.
I added
test/release-keeper-swap.test.tstoSLOWinscripts/gate.tsinstead of making the test faster. The gate andtscare clean, and the 8 tests thatscripts/fast.tsnames pass (119 tests). Closes #12790.The flagged test, "land, swap, verify, bad release, swap back", starts real stand-in processes. It swaps two in and one back while a client keeps hitting the port, and it polls each swap until the new process answers. A 2.66 s run on a loaded shard is that work, not a flake. Cutting it down would mean dropping the zero-refused-requests check, which is the point of the test.
The new entry cites #12790 as its owning issue and gives the reason as "2.7 s a test on the gate box". I did not shorten the polling waits or split the story into smaller tests; either could bring it back under 2 s.
I ran the file once alone and all 11 tests pass in 3.65 s. I did not run
--rerun-each 10, so I have not measured how much the time varies.Closes #12790