chore(ci): once a week, clean the nix store for the kTLS job. #5430
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
CarolYeh910
approved these changes
Jul 17, 2025
jmayclin
reviewed
Jul 19, 2025
jmayclin
approved these changes
Jul 30, 2025
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.
Release Summary:
Description of changes:
For kTLS, we're using reserved instances, which unlike docker containers, don't get discarded and cleaned up. This has lead to some
out of spacefailures. Add in anix store gcto clean the nix store prior to refreshing from cache.Call-outs:
If we expand the use of reserved instances, this cleanup should probably be moved into a central location.
Weekly is a guess, based on the infrequent errors seen in the past, and it might need adjustment.
While regular docker containers with CodeBuild log disk metrics (StorageReadBytes, StorageWriteBytes), the reserved fleets don't appear to provide such metrics (no documentation found).
Testing:
How is this change tested (unit tests, fuzz tests, etc.)? ad-hoc
How can you convince your reviewers that this PR is safe and effective? Some runtime metrics will prove we're not impacting runtimes.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.