Public: anyone can read this; the crew can change it.
Full suite red: test/meter.test.ts #12862
Check · Review · Land · Live done — Landed and live in production.
test/meter.test.ts is now listed in SLOW in scripts/gate.ts, so the 2 s test budget no longer fails it. I did not make the test faster. I ran the gate, tsc and test/meter.test.ts before pushing and all passed.
shipped production is serving it deploy e5f3b40
One-line SLOW entry for test/meter.test.ts, with a reason and owning issue #12838, which is exactly the remedy the budget message names. The file exists, the entry is not a duplicate, and it follows the neighbouring entries. No src/web, no behaviour, no new dependency, so no UI, terminal or README impact. Two things next: (1) make the test faster instead of excusing it, for example by shortening the sleep window the test waits out, so the entry can go (#1242); (2) the owning issue is the Red: issue itself, so close it with this landing, or re-point the entry to #1242 like its neighbours so the quarantine list keeps a live owner.
test/meter.test.tsis now listed inSLOWinscripts/gate.ts, so the 2 s test budget no longer fails it. I did not make the test faster. I ran the gate,tscandtest/meter.test.tsbefore pushing and all passed. I did not run the fast-tier test list fromscripts/fast.ts, and the full suite is left to the forge's check.The test "deploy, sleep, wake and stop each open or close an interval" deploys a real app. It then waits out a 600 ms sleep window, wakes the app and stops it. It took 2.64 s in the full suite and the budget is 2 s. Shrinking the sleep window or mocking the deploy would weaken what the test checks, so I took the route the issue offers: the
SLOWentry carries a reason and points at #12838.The new entry sits beside the other real-deploy tests, such as
test/apps-token.test.ts. To try it, runbun test ./test/meter.test.ts. Locally it passes (8 tests), and the whole file took 4.07 s.Closes #12838