Skip to content

Conversation

kshyatt
Copy link
Member

@kshyatt kshyatt commented Aug 27, 2025

cuDNN 9.12 doesn't work with CUDA 11.

cuDNN 9.12 doesn't work with CUDA 11.
Copy link

codecov bot commented Aug 27, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.76%. Comparing base (6ca192d) to head (bd37d7e).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff             @@
##           master    #2861       +/-   ##
===========================================
+ Coverage   77.25%   89.76%   +12.51%     
===========================================
  Files         150      150               
  Lines       13162    13249       +87     
===========================================
+ Hits        10168    11893     +1725     
+ Misses       2994     1356     -1638     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@kshyatt kshyatt requested a review from vchuravy August 28, 2025 05:21
@kshyatt
Copy link
Member Author

kshyatt commented Aug 28, 2025

OK I'm going to merge this to hopefully unbreak the builds. We can always revert it later.

@kshyatt kshyatt merged commit 3da87de into master Aug 28, 2025
2 checks passed
@kshyatt kshyatt deleted the ksh/cudnn_compat branch August 28, 2025 17:09
Copy link
Member

@vchuravy vchuravy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah yes classic semantic versioning...

Thanks @kshyatt

@kshyatt
Copy link
Member Author

kshyatt commented Aug 29, 2025

@vchuravy should we now tag a new version of cuDNN to protect people, then we can reloosen the bound?

@kshyatt
Copy link
Member Author

kshyatt commented Aug 29, 2025

Or rather, we should tag a new version after #2855 is merged...

@vchuravy
Copy link
Member

We might also have to go I to the registry and fix the information there?

@kshyatt
Copy link
Member Author

kshyatt commented Aug 29, 2025

You mean for the current version of cuDNN?

@maleadt
Copy link
Member

maleadt commented Sep 1, 2025

Also need to do the same for cuTENSOR, which has a loose bound on its JLL too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants