Skip to content

[6.2][SwiftScanCAS] Make sure that CAS size limitation can take effect #1868

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

Open
wants to merge 1 commit into
base: release/6.2
Choose a base branch
from

Conversation

akyrtzi
Copy link
Contributor

@akyrtzi akyrtzi commented Apr 9, 2025

Previously the last CAS instance that was closing the database was not the one that was getting the CAS size limitation setting, resulting in the limit not being in effect.

rdar://148836977
(cherry picked from commit 7134aa1)

Description: CAS size limitation for swift caching cannot take effect due to the last CAS database instance that closes the database is not the one exposed to the build system that gets the size limit.
Origination: N/A
Radar: rdar://148836977
Risk: Low.
Tested: Added unit test
Reviewed by: @cachemeifyoucan

Previously the last CAS instance that was closing the database was not the one
that was getting the CAS size limitation setting, resulting in the limit not being in effect.

rdar://148836977
(cherry picked from commit 7134aa1)
@akyrtzi
Copy link
Contributor Author

akyrtzi commented Apr 9, 2025

@swift-ci Please test

@akyrtzi akyrtzi requested a review from cachemeifyoucan April 9, 2025 17:21
@akyrtzi
Copy link
Contributor Author

akyrtzi commented Apr 11, 2025

@swift-ci Please test

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