Bind package cache finalization to its owning process - #1606
Merged
Conversation
TheGreenCedar
marked this pull request as ready for review
July 29, 2026 21:26
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.
Context
Frozen-candidate qualification run 30487492458 built Linux successfully inside the pinned glibc container. That container reported 1,130 sccache requests and stopped its own server. The later host finalizer then tried to stop a host server that never compiled anything and failed with connection refused.
The regression came from removing the Linux host qualification-driver build while broadening the host finalizer to every successful Linux container build.
Base:
07451c4842ea8e9a635bf3940a25c1177db557aaHead:
7291b522a0366b938c5ad78bcb268630418f7789Tree:
50065b657546b76e9f8a01b32ad0d3a36654e895What changed
PATH.The package matrix, job DAG, evidence cells, and release claim graph do not change, so
release-claims.jsonremains unchanged.Verification
a0fe8005daf3bb5e593f2637d2d2f245cd787e311fae6a24b962b511d2960c4f.PATH/GITHUB_ENV/NODE_OPTIONS, forged outputs, binary replacement, selector widening, absorbing shells, quote escapes, duplicate decoys, moved steps, disabled hash checks, and PATH invocation; all were rejected.960e7071ba1e97425a9c0be13dc107dd35374bd8e9a6ed49fc522d1aa85062ac.git diff --checkpassed.7291b522a0366b938c5ad78bcb268630418f7789.Release sequence
After merge, integrate this repair into #1597, restore the complete unfrozen pre-calibration constant set, recalibrate on that new exact head, freeze only the generated constant set, and run frozen-candidate qualification once. The previous calibration receipt is invalidated and will not be reused.
Refs #1597
Closes #1605