Intent: perimeter mediums (#2922) in test/perimeter-mediums.test.ts goes red in pulls that never touch it (pull #5076), so good work is parked and the board shows red noise.
Done:
[ ] the pull names the cause (wall clock, a real sleep, a shared port or directory, a fake clock mixed with Date.now(), a budget measured end to end instead of in the code it guards)
[ ] bun test --rerun-each 30 test/perimeter-mediums.test.ts passes, and also passes with other test files running beside it (bun test test/perimeter-mediums.test.ts test/apps.test.ts). The pull says how it was checked
[ ] the test still fails when the behaviour it guards is broken; what it promises about the product is unchanged. A time or resource budget may only move to what the code itself spends, never just get wider
Files: test/perimeter-mediums.test.ts; the source only if the flake is a real race there (then the pull says so).
Hint: find which medium's request depends on timing or a shared port, and make it deterministic.
Intent:
perimeter mediums (#2922)in test/perimeter-mediums.test.ts goes red in pulls that never touch it (pull #5076), so good work is parked and the board shows red noise.Done:
bun test --rerun-each 30 test/perimeter-mediums.test.tspasses, and also passes with other test files running beside it (bun test test/perimeter-mediums.test.ts test/apps.test.ts). The pull says how it was checkedFiles: test/perimeter-mediums.test.ts; the source only if the flake is a real race there (then the pull says so). Hint: find which medium's request depends on timing or a shared port, and make it deterministic.