Skip to content

[CAS] Make CAS plugin options to be cache invariant #76835

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 3, 2024

Conversation

cachemeifyoucan
Copy link
Contributor

Do not add CAS configurations into cache key computation. This ensure if the cache keys are identical if two functionally equivalent plugins are used. This is safe to do because if any of the CAS configurations changes how the cache key is computed, they are going to be directly reflected in the cache key without adding its configuration into the key.

rdar://137091843

Do not add CAS configurations into cache key computation. This ensure if
the cache keys are identical if two functionally equivalent plugins are
used. This is safe to do because if any of the CAS configurations
changes how the cache key is computed, they are going to be directly
reflected in the cache key without adding its configuration into the
key.

rdar://137091843
@cachemeifyoucan
Copy link
Contributor Author

@swift-ci please smoke test

@cachemeifyoucan cachemeifyoucan merged commit f92b1e4 into swiftlang:main Oct 3, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants