workaround troubled cupy 12x package#1368
Merged
garrettwrong merged 1 commit intodevelopfrom Mar 23, 2026
Merged
Conversation
moving to cuda 13 for 2026
j-c-c
approved these changes
Mar 23, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #1368 +/- ##
========================================
Coverage 90.84% 90.84%
========================================
Files 135 135
Lines 14658 14658
========================================
Hits 13316 13316
Misses 1342 1342 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Collaborator
Author
|
I think we can safely merge this guy in. |
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
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 will work around the most recent (14.0.0 and 14.0.1)
cupy-cuda12xhaving issues. It was released end of Feb 2026, so the package version enforced in this PR is actually what was running for the entirety of the 12x timeline.Plan is to move up to CUDA 13x for 2026 in a separate PR and deal with any issues relating to that (hopefully none, alas) specifically there.