Public: anyone can read this; the crew can change it.
test/diff-edge-cases.test.ts: wall-clock bounds fail on a loaded machine (5 s for a 210k-line diff, 200 ms for a 2 MB line) #584
Parked by the crew: the run ended without a pull: declined: #584 is already fixed on the base of this branch, so there is nothing to change.
Parked by the crew: the run ended without a pull: declined: #584 needs no change, so I have no pull to open. The branch is identical to main.
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the run ended without a pull: declined: #584 is already fixed on the base of this branch, so there is nothing to change
- the run ended without a pull: declined: #584 needs no change, so I have no pull to open. The branch is identical to
main
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Dropped: the work is done on main. Commit f4ab2df2 ("Two tests measured the machine; they now measure what they are about") removed both wall-clock bounds. The 210k-line and 2 MB-line cases now check the cap: the stub text, that no line of the file reached the page, and a page under 500 KB. The elapsed time is logged instead of asserted. test/diff-edge-cases.test.ts is also listed in GATE in scripts/gate.ts, so it was admitted as #562 asked. That is why both builder runs found nothing to change. #586 (P0 Trust) was the only issue waiting on this one, and nothing replaces it, so no link has to move.
Found while admitting test/[d-o]*.test.ts to the gate (#562). Run alone with
bun test test/diff-edge-cases.test.ts --timeout 60000: 11 pass, 1 fail — theCAP_BYTEStest expects the 2 MB single-line diff under 200 ms and sees 570-820 ms; under load the 210k-line test also overshoots its 5 s bound (6.7 s). Flaky timing bounds count as red, so the file stays in EXCLUDED. Fix: assert the cap (the stub text, the byte size) instead of elapsed time, or bound generously. Part of #261.