A red Server-Timing sweep names the route that failed and why, so a one-off failure in the full suite can be diagnosed from its log #9502

When the Server-Timing sweep goes red now, its log says which page failed and why. It no longer stops on the first failure with no route attached.

What moved where: the loop that fetches each page moved out of test/server-timing-sweep.test.ts into a plain function, collectTimings, in the new file test/helpers/timing-sweep.ts. It runs any fetch over a list of paths, four at a time, and sorts each page into one of these lists:

• named: pages that name session and render
• bare: pages that don't
• redirected: pages that answer 3xx
• failures: pages that throw (abort, reset) or answer 5xx, each as { path, status } or { path, error }
• missingApp: pages whose Server-Timing leaves out app, each as { path, serverTiming }

In the sweep:

• Nothing is asserted inside the loop any more. expect(failures).toEqual([]) and expect(missingApp).toEqual([]) each run once at the end, so a red run lists every bad route at once.
• Each request now gives up after 20 s, down from 60 s, under the test's 120 s cap. A slow page then shows up by name in failures instead of timing out the whole test. A comment in the test says why.
• The redirect and debt assertions are unchanged.
• A 5xx page now counts as a failure even if its Server-Timing header looks right, so the sweep is slightly stricter than before.

New unit tests:

• One feeds collectTimings a fake fetch with six pages: one throws, one answers 500, one has no app, plus a named page, a bare page and a redirect. It checks that each path lands in the right list.
• Another uses a page that never answers and a 20 ms limit, and checks that it comes back as a timeout entry naming /slow.

What I chose not to do: no change to src/, because no real page failed. I did not try to reproduce the old failure from #9407. The keep_plan tool the issue mentions isn't available in this run, so the issue has no plan on it.

How to try it: bun test test/server-timing-sweep.test.ts passed three runs in a row: 4 pass, 0 fail, about 2.7 s each. bun scripts/gate.ts and bun x tsc --noEmit are both clean.

🤖 Generated with Claude Code

Closes #9500

When the Server-Timing sweep goes red now, its log says which page failed and why. It no longer stops on the first failure with no route attached.

What moved where: the loop that fetches each page moved out of test/server-timing-sweep.test.ts into a plain function, collectTimings, in the new file test/helpers/timing-sweep.ts. It runs any fetch over a list of paths, four at a time, and sorts each page into one of these lists:

• named: pages that name session and render
• bare: pages that don't
• redirected: pages that answer 3xx
• failures: pages that throw (abort, reset) or answer 5xx, each as { path, status } or { path, error }
• missingApp: pages whose Server-Timing leaves out app, each as { path, serverTiming }

In the sweep:

• Nothing is asserted inside the loop any more. expect(failures).toEqual([]) and expect(missingApp).toEqual([]) each run once at the end, so a red run lists every bad route at once.
• Each request now gives up after 20 s, down from 60 s, under the test's 120 s cap. A slow page then shows up by name in failures instead of timing out the whole test. A comment in the test says why.
• The redirect and debt assertions are unchanged.
• A 5xx page now counts as a failure even if its Server-Timing header looks right, so the sweep is slightly stricter than before.

New unit tests:

• One feeds collectTimings a fake fetch with six pages: one throws, one answers 500, one has no app, plus a named page, a bare page and a redirect. It checks that each path lands in the right list.
• Another uses a page that never answers and a 20 ms limit, and checks that it comes back as a timeout entry naming /slow.

What I chose not to do: no change to src/, because no real page failed. I did not try to reproduce the old failure from #9407. The keep_plan tool the issue mentions isn't available in this run, so the issue has no plan on it.

How to try it: bun test test/server-timing-sweep.test.ts passed three runs in a row: 4 pass, 0 fail, about 2.7 s each. bun scripts/gate.ts and bun x tsc --noEmit are both clean.

🤖 Generated with Claude Code