ci: move cache job to python3.13 for memory issue#4713
Merged
Conversation
Cache job is getting killed early, I think because we're running out of memory because the sheer number of CVEs has gotten too large. Things seem to work better on python 3.13 (likely due to other memory improvements) so this is an attempt at a temporary workaround while we address the underlying issue. Signed-off-by: Terri Oda <[email protected]>
We're stuck in a loop: the longtests can't run because the cache job failed, but I can't fix the cache job because the longtests won't pass. This should help us break out of the loop for now until the repo settings can be changed. Signed-off-by: Terri Oda <[email protected]>
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
1 participant
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.
Cache job is getting killed early, I think because we're running out of memory because the sheer number of CVEs has gotten too large. Things seem to work better on python 3.13 (likely due to other memory improvements) so this is an attempt at a temporary workaround while we address the underlying issue.