Repository navigation
fix(ci): avoid unnecessary mutation cache misses - #62
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.
Two avoidable cache misses triggered fresh mutation work: a rejected exact own-PR cache prevented admission of an already downloaded compatible main baseline, and two editorial README files were still fingerprinted.
After own-PR admission fails, the runner now tries the existing main envelope before cleanup or cold routing. A valid authenticated main SHA is required, and the same input-key, source-identity and current-policy audit remain mandatory. The admitted source determines audit provenance. Valid PR reports stay preferred; forced runs and execution/audit failures retain their existing behavior.
Exclude only
fuzz/README.mdandscripts/schemas/cyclonedx-1.5/README.md. JSON schemas, fuzz resources, neighboring Markdown and all other existing executable inputs remain keyed. This adds a ten-line guarded retry, two declaration changes and two exact-path exclusions; it introduces no dependency analysis, transport search, cache engine or workflow change.Validation:
273888bpreserved the seven-file patch byte-for-byte; all 41 incoming paths exactly match main. The 58 routing/input tests and 14 admission/promotion tests passed on refreshed head235c809, and independent integration review found no issues.npm run checkstopped on six previously observed Windows HTTP cleanup failures: 2,125 passed and 12 skipped. The complete cache/routing run separately retained the unchanged Windows chmod fingerprint failure (65/66). No unrelated assertions were changed.The runner fixture mocks process/discovery/audit boundaries; the native toy proves native reuse and input invalidation, not hosted authentication or full production-parser acceptance. Required hosted exact-head CI 40633094641 passed: 34/34 jobs and 39/39 checks, including 733 tooling tests, 162 policy tests, all 15 native fixture scenarios, and the full parser collector (1,360 mutants, 100% adjusted). The tested synthetic merge tree matches reviewed head
235c809. The live route was cold after incompatible main admission; rejected-PR-to-valid-main fallback is covered by the harness, not claimed as live-transport coverage. No long exploratory mutation campaign, settings change or release action.