Skip to content

test: lift scaling guards above runner noise floor - #8

Merged
rahlk merged 1 commit into
mainfrom
fix/issue-7-scaling-test-noise
Sep 6, 2026
Merged

test: lift scaling guards above runner noise floor#8
rahlk merged 1 commit into
mainfrom
fix/issue-7-scaling-test-noise

Conversation

@rahlk

@rahlk rahlk commented Sep 6, 2026

Copy link
Copy Markdown
Collaborator

Closes #7.

The two wall-clock scaling guards in internal/dialects/helm/templates_test.go compared a 4x larger input against small*8 + 25ms / small*9 + 50ms. On a shared runner the small measurement is ~12 ms, so ordinary noise on the large run tripped the bound (PR #6 ci run 34002119560: 166ms vs 158ms), and release.yml uses make test as its tag gate.

Change: input sizes raised to 22k/88k and 24k/96k so the small measurement is ~50 ms on a fast machine (further above the noise floor on a runner). Best-of-3, the ratio multipliers, the 4x ratio, and the 5 s ceiling are unchanged; the parser is untouched.

Evidence: with a test-local injected O(n²) loop the dense guard fails (96k took 1.24s after 24k took 120ms; want <= 1.13s), then passes after reverting; -run ScalesNearLinearly -count=30 60/60. Added local test time is about one second (0.95–1.05 s across runs).

The 10k/2k small measurements landed near CI's noise floor (~12ms),
so ordinary scheduler/GC jitter on the large run could trip the
ratio bound and abort a release. Raise the sizes so the small
measurement clears ~50ms on a typical runner while keeping the same
ratio bounds, best-of-3, and absolute ceiling.
@rahlk
rahlk merged commit e8ee695 into main Sep 6, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Flaky wall-clock scaling tests can fail CI and the release gate

1 participant