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
@@ -103,7 +103,8 @@ describe("plan codes", () => {
    expect(pattern("PLAN_CODE")).toBe(PLAN_CODES.map(js).join("|"));
  });

-  it("are not cited in the code", () => {
+  // Reads every tracked and new file of the repo: ~0.6 s idle, past 5 s on a busy machine's disk and CPU.
+  it("are not cited in the code", { timeout: 30_000 }, () => {
    const files = tracked();
    expect(files.length).toBeGreaterThan(1000); // a scan that reads nothing is green over nothing
    const hits = files.flatMap((f) =>