Repository navigation
test: widen the dense fallback CPU ratio guard to 1.10 - #1185
Merged
Merged
Conversation
kvlonge
enabled auto-merge (squash)
October 21, 2026 00:08
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The dense delta edit-loop guard caps a fallback compile at 1.05x a full compile's median CPU. Across 33 recent passing CI runs the ratio was 0.97–1.04 (median about 1.017): fallback costs about 2% more by design, plus about ±3% runner noise. It failed two unrelated PRs at 1.050 and 1.053.
Changes
expected_max_fallback_cpu_ratiofrom 1.05 to 1.10 for the 3,000- and 10,000-model cases. A fallback that repeats compile work still shows about 2.0x and fails.Verification