Repository navigation
Project hosted lane wall time from measured worker ratios - #139
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.
Hosted parallel shares were taking about twice the planner's largest-worker estimate, leaving the shard check green close to the hosted failure threshold. This records each share's wall time alongside its original planned worker time, retains paired calibration during refresh, and uses the lane's maximum recorded ratio to project hosted time.
Parallel shards and CI matrix rows increase from four to six. Existing worker and hosted wall failures remain; calibrated overload requires another shard below the cap and reports a numerical warning at the cap. Budgets, targets and the cap are unchanged. The checked-in calibration comes from a digest-verified historical plan and projects the slowest parallel share at about 239.8 seconds, a 59.8-second residual over the 180-second target.
Part of #133
Validation: all 11 local milestone gates pass on Python 3.13.15 and 3.14.8 against this frozen head; fresh independent final audit is CLEAN after both preserved findings were corrected. Hosted share measurements will follow this PR run.