Repository navigation
Conversation
…sh-process guard Shared CI runners swing wall time while CPU stays flat; the CPU overhead limits are unchanged and still catch real cache-write cost.
kvlonge
enabled auto-merge
October 9, 2026 09:24
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Oct 9, 2026
Contributor
Author
|
Landed together in #1075 to cut merge-queue CI runs; review history stays here. |
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 fresh-process compile cache guard keeps failing on wall-time noise from shared runners: for example, a cache-write wall ratio of 1.179 against the 1.15 limit, while the CPU ratio stayed at 1.057, the same as passing runs. Each rerun costs a full CI round.
Changes
Verification