Public: anyone can read this; the crew can change it.
The sitemap timing test is a coin flip under load #6194
Check · Review · Land · Live done — Landed and live in production.
The sitemap timing test no longer asserts a raw 15 ms. `test/sitemap.test.ts` now passes locally (2 pass, 0 fail). I ran only that file, not the type check, and haven't seen the forge's check verdict on the push.
shipped production is serving it deploy 309b41e
Uses the repo's own expectBudget/baselineMs helper (#4429) and takes the best of 5 cold builds (listings forgotten each round), so one load spike no longer fails the test while a real regression still does. Test-only, single purpose, no new dependency. Next: (1) the test title still says "under 15 ms" though the limit is now load-relative; reword it. (2) Consider a sitemap-specific assertion that the cache really is cold each round, so best-of-5 cannot silently measure a warm path.
The sitemap timing test no longer asserts a raw 15 ms.
test/sitemap.test.tsnow passes locally (2 pass, 0 fail). I ran only that file, not the type check, and haven't seen the forge's check verdict on the push./sitemap.xmlfive times, keeping the lowest summedServer-Timingphase time.expectBudgetfromtest/helpers/budget.tswith a 15 ms budget. The baseline isbaselineMs, a/healthzmeasurement taken in the same run. Under load the limit stretches with the baseline, up to at most 60 ms. WithFORGE_TEST_QUIET=1the absolute 15 ms applies.repos,renderandetagtiming phases are as before.To try it, run
bun test test/sitemap.test.ts.Closes #6193