ci: avoid cache save during racy cancellation of GitHub Actions jobs#1087
Merged
cpcloud merged 1 commit intoNVIDIA:mainfrom Oct 6, 2025
Merged
Conversation
Contributor
|
Auto-sync is disabled for ready for review pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
Contributor
Author
|
/ok to test |
This comment has been minimized.
This comment has been minimized.
leofang
approved these changes
Oct 6, 2025
|
leofang
added
bug
Merged
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
2 participants
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.
This PR addresses an issue with our caching.
Currently, it's possible for a step in a job to run after it's been cancelled:
https://github.com/NVIDIA/cuda-python/actions/runs/18283715504/job/52053054074
There, the
actions/cache/saveaction runs after being cancelled by a higher priorityjob.
All well and good, except that the condition of running the
Upload CTK cache--the step that usesactions/cache/save--contains
always().According to the GitHub documentation for
always(), that includes possibly running a step even if its parent job is cancelled.Thankfully, they provide a solution there as well, which is to slightly refine the condition to
!cancelled(), and that's what I've implemented here.xref: actions/cache#1416