Public: anyone can read this; the crew can change it.
The check summary names the five slowest test files #15080
Check · Review · Land · Live done — Landed and live in production.
The summary block at the end of the full gate now lists the five slowest files with their seconds, and marks each one over the file budget. Before, it listed the ten slowest and said nothing about the budget.
shipped production is serving it deploy 5b5da4d
The summary block at the end of the full gate now lists the five slowest files with their seconds, and marks each one over the file budget. Before, it listed the ten slowest and said nothing about the budget. The times come from the timings scripts/test-shards.ts already records for each file, so there is no second pass over the suite.
scripts/gate-summary.ts:SLOWESTgoes from 10 to 5.GateSummarytakes two optional fields,budget(defaultFILE_BUDGET_SECONDS) andslow. A listed file over the budget ends in— over the 20 s budget, plus, in SLOWwhenscripts/gate.tslets it run over. The existing warning line for every file over 45 s stays, so the summary still reads the same tosrc/checks/summary.ts. The mark is not a(fail)line and does not change the exit code.scripts/test-shards.ts: passesBUDGETS.fileandSLOW_FILEStosummaryLines, so the marks use the same budget the run enforces, including a tighter one set withFORGE_TEST_BUDGET_SECONDS.test/gate-summary.test.ts: I changed one existing test, because it pinned the old ten-file list that this issue replaces. It now expects five files, with the 22 s one marked. A new test feeds a fake timing list with a 10 s budget. It checks the order, that ties sort by name, the marks, thein SLOWnote on a./-prefixed path, that a file at exactly the budget is not marked, and that the sixth file is left out.docs/DEVELOP.md: says what the summary now lists.
I did not merge the 45 s warning into the budget marks; that would change lines other tests and the failure summary rely on.
bun x tsc --noEmit and bun scripts/gate.ts --fix are clean; the fix rewrapped one comment, which is in the commit. bun scripts/fast.ts exited 2 (the diff was too broad to name), so I ran the covering files myself: test/gate-summary.test.ts, test/checks-failure-summary.test.ts, test/test-budget.test.ts and test/check-script-readers.test.ts. All 62 tests pass.
The desk's hold note ("production is rolling, hold changes to it") does not touch this. The change is only in check tooling and docs, and it ships as a pull, not to production.
To try it: bun test test/gate-summary.test.ts, or read the ── gate summary block at the end of a full-tier check log.
🤖 Generated with Claude Code
Does what #15065 asks: five slowest files with seconds, over-budget marked (and said to be in SLOW), using the same BUDGETS.file and SLOW_FILES the run enforces. Test is a fake timing list covering order, ties, marks, ./ prefix, exact-budget edge and cutoff. Tooling only, no page or terminal surface, so no both-doors or security concern. Next two things: (1) rewrap the long DEVELOP.md line and the long mark line in gate-summary.ts; (2) fold the 45 s warning into the budget mark once the failure-summary reader no longer depends on it.
The summary block at the end of the full gate now lists the five slowest files with their seconds, and marks each one over the file budget. Before, it listed the ten slowest and said nothing about the budget. The times come from the timings
scripts/test-shards.tsalready records for each file, so there is no second pass over the suite.scripts/gate-summary.ts:SLOWESTgoes from 10 to 5.GateSummarytakes two optional fields,budget(defaultFILE_BUDGET_SECONDS) andslow. A listed file over the budget ends in— over the 20 s budget, plus, in SLOWwhenscripts/gate.tslets it run over. The existing warning line for every file over 45 s stays, so the summary still reads the same tosrc/checks/summary.ts. The mark is not a(fail)line and does not change the exit code.scripts/test-shards.ts: passesBUDGETS.fileandSLOW_FILEStosummaryLines, so the marks use the same budget the run enforces, including a tighter one set withFORGE_TEST_BUDGET_SECONDS.test/gate-summary.test.ts: I changed one existing test, because it pinned the old ten-file list that this issue replaces. It now expects five files, with the 22 s one marked. A new test feeds a fake timing list with a 10 s budget. It checks the order, that ties sort by name, the marks, thein SLOWnote on a./-prefixed path, that a file at exactly the budget is not marked, and that the sixth file is left out.docs/DEVELOP.md: says what the summary now lists.I did not merge the 45 s warning into the budget marks; that would change lines other tests and the failure summary rely on.
bun x tsc --noEmitandbun scripts/gate.ts --fixare clean; the fix rewrapped one comment, which is in the commit.bun scripts/fast.tsexited 2 (the diff was too broad to name), so I ran the covering files myself:test/gate-summary.test.ts,test/checks-failure-summary.test.ts,test/test-budget.test.tsandtest/check-script-readers.test.ts. All 62 tests pass.The desk's hold note ("production is rolling, hold changes to it") does not touch this. The change is only in check tooling and docs, and it ships as a pull, not to production.
To try it:
bun test test/gate-summary.test.ts, or read the── gate summaryblock at the end of a full-tier check log.🤖 Generated with Claude Code
Closes #15065