-
Notifications
You must be signed in to change notification settings - Fork 25.1k
Move trunk windows builds to CUDA-12.4 #145844
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
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/145844
Note: Links to docs will display an error until the docs builds have been completed. ⏳ No Failures, 7 PendingAs of commit d5e5e6e with merge base 97b3b73 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
Was this just an accidental miss from upgrading 12.4? |
@janeyx99 need to add it to our runbook https://github.com/pytorch/builder/blob/main/CUDA_UPGRADE_GUIDE.MD |
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.
LGTM, but can we have some sort of an organized migration plan (there were dozen or so of CUDA-12.1->CUDA-12.4 migration PRs that picked up various leftovers)
Agree on this planning on adding all these PRs to the runbook: pytorch/builder@main/CUDA_UPGRADE_GUIDE.MD I believe it needs to be updated. |
@pytorchmergebot merge -f "lint and windows build is green" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Same as : #130446
That should catch build regressions that were previously only detectable during the nightly builds for 12.4