-
Notifications
You must be signed in to change notification settings - Fork 21.5k
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
[BE]: Update cudnn to 9.1.0.70 #123475
[BE]: Update cudnn to 9.1.0.70 #123475
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/123475
Note: Links to docs will display an error until the docs builds have been completed. ❌ 27 New Failures, 7 Unrelated FailuresAs of commit 8d85d49 with merge base 0de6d24 ( NEW FAILURES - The following jobs have failed:
FLAKY - The following jobs failed but were likely due to flakiness present on trunk:
UNSTABLE - The following jobs failed but were likely due to flakiness present on trunk and has been marked as unstable:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
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.
Looks good assuming you fix the Caffe2 issue.
@Skylion007 do we anticipate #122527 landing in the near-future? caffe2 fixes might be involved and look something like #115719 which might be unnecessary if caffe2 is being removed soon |
@eqy - I'm still working on eliminating caffe2, but having difficulty isolating all the issues - I haven't worked deeply with PyTorch's build before. |
9.1.1 is out |
@pytorchmergebot rebase (checking to see if caffe2 issue has been resolved) |
❌ 🤖 pytorchbot command failed:
Try |
@pytorchmergebot rebase |
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
Successfully rebased |
82402a0
to
e202627
Compare
@eqy Looks like the issues were fixed. Let's merge. |
@pytorchmergebot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Merge failedReason: 1 mandatory check(s) failed. The first few are: Dig deeper by viewing the failures on hud |
@pytorchmergebot rebase |
Run ./github/regenerate.sh after modifying scripts/generate_binary_build_matrix.py
Testing cudnn v9 changes with pinned docker image and builder PR Arm CUDA will unfortunately still fail due to pinned buggy(for arm only, x86_64 ok) docker image
This reverts commit 86172c5.
@pytorchmergebot merge -f "lint 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 |
cuDNN has managed to upload cu11 and cu12 wheels for ~~9.0.0.312~~ 9.1.0.70, so trying this out... CC @Skylion007 @malfet Co-authored-by: Wei Wang <weiwan@nvidia.com> Co-authored-by: atalman <atalman@fb.com> Pull Request resolved: pytorch#123475 Approved by: https://github.com/Skylion007, https://github.com/malfet, https://github.com/nWEIdia, https://github.com/atalman
cuDNN has managed to upload cu11 and cu12 wheels for
9.0.0.3129.1.0.70, so trying this out...CC @Skylion007 @malfet
cc @csarofeen @ptrblck @xwang233 @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @chauhang