Files
pad/internal
xarmian 24833331ff test(links): mention linearity tests compare n with 4n, not an absolute bound (BUG-3995) (#2262)
* test(links): mention linearity tests compare n with 4n, not an absolute bound (BUG-3995)

TestExtractMentionsLinearAfterCodeSpans failed CI under -race at 3.08 s
against its 3 s bound (#2259). Both mention linearity tests, it and its
sibling TestExtractMentionsLinearOnSlashRuns, now share
assertMentionsLinear: best of five runs at n and 4n, each after a
runtime.GC(), and the ratio must stay under 8x (about 4x when linear,
about 16x when quadratic). A 30 s per-run backstop stops a regressed scan
from running the suite for minutes. No absolute bound remains.

Claude-Session: https://claude.ai/code/session_01EZ6hZzQiytCeBxXrtCWcVd

* test(links): the mention linearity helper's comment bounds its claim (BUG-3995 r1)

It said a slow runner "cannot fail" the check and that the backstop stops
a regressed scan "running the suite for minutes". The 30 s per-run
backstop is absolute, and a regressed run measured 1.5 to 3 minutes before
failing. The comment now says what is true: the ratio is independent of
runner speed, and the backstop is about 16x the slowest linear run measured.

Claude-Session: https://claude.ai/code/session_01EZ6hZzQiytCeBxXrtCWcVd
2026-10-20 15:58:18 -04:00
..