test: tests that assumed an idle machine wait for what they assert, or carry a budget for their work

Under a busy machine (the gate's lanes side by side, 12 busy cores) these went red at random: a press landed while the button was still busy, an answer was settled before it was asked for, a page grew past one wait's budget, a lazy chunk was transformed inside a 1 s wait, focus was taken a frame after the press. They now wait for the condition they depend on, preload the chunks they open, and the tests that do heavy work (whole-repo scans, the type-aware linter, module resets) carry an explicit budget naming that work. The whole suite four times under 12 busy-loop processes: red 4/4 before, 0/4 after.
2026-10-17 01:08:15 +02:00
parent 926e5e9899
commit 5ba5679239
18 changed files with 181 additions and 96 deletions
@@ -38,7 +38,8 @@ function files(dir: string): string[] {
 }

 describe("removed features stay removed", () => {
-  it("leaves no trace of the demo account", () => {
+  // Reads every source file of the repo: ~0.4 s idle, past 5 s on a busy machine's disk and CPU.
+  it("leaves no trace of the demo account", { timeout: 30_000 }, () => {
    const hits = ROOTS.flatMap(files)
      .filter((f) => !ALLOWED.has(f))
      .flatMap((f) =>