Repository navigation
test: tighten macro-rich fresh-process cache budgets - #785
Merged
Merged
Conversation
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
#782 made the fresh-process cache guards macro-rich, with provisional limits. Its CI run now gives measured runner times. The provisional limits allowed up to 1.7x those times, enough headroom to hide a real regression.
Changes
Limits are set to about 1.25x the slowest CI time for each phase on #782:
CI slowest times:
The 5000-model cold limit rises from 23s to 24s: at 23s its project-config edit had only 1.19x headroom. The 0.67 warm-to-cold ratio guard is unchanged (CI measured 0.54–0.58).
Verification
ruff format --checkandruff checkpass on the changed file.