-
Notifications
You must be signed in to change notification settings - Fork 161
CI: Install latest compute-sanitizer separately from CTK #594
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
Conversation
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. |
/ok to test 3f07930 |
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line needs to become mkdir -p
to allow reusing the same folder
https://github.com/NVIDIA/cuda-python/pull/594/files#diff-c3ca06d8e9146d2421ea02333d7a174f5a0c195d661e9327a5eb1b30790f6decL54
/ok to test 9aa44f9 |
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
Actually, we don't want to use the same folder. We want to ensure the folder is clean so that we only get the components that we asked for? |
Prevent collision with components already installed to the CUDA_PATH
/ok to test 6b02f1a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@carterbox sorry for late reply, I have a horrible schedule today. I suggest to not waste time on this PR and merge your other PR instead. This PR would not work without significant overhaul as explained in the offline chat. We’re blowing up the GitHub Cache space because the second invocation of fetch_ctk
is separately cached, with the mini ctk from the previous step + sanitizer.
hmmm I dunno why this PR was closed, I feel we can repurpose it if we can fix the caching issue, Daniel explained the latest changes to me offline (which I overlooked, sorry!) |
/ok to test 287302b |
/ok to test 1d9749e |
/ok to test c7f9982 |
/ok to test b9fabb6 |
/ok to test 0451990 |
/ok to test 69b6ee1 |
/ok to test b2c6de3 |
/ok to test 5376e79 |
/ok to test 5376e79 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome that you succeeded in wrestling this down 🚀
Thanks, @carterbox and @rwgk! This should make it look a lot nicer and robust now. With this PR, each invocation of The biggest challenge is still that |
|
Description
We want to always use the latest compute-sanitizer because there could be bug fixes for the compute-sanitizer, and it is OK to use the newest compute-sanitizer on programs running with old CTK versions.
This PR reverts #593
Checklist