-
-
Notifications
You must be signed in to change notification settings - Fork 596
Close CUDA 11.8 migration #5340
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
Merged
jakirkham
merged 2 commits into
conda-forge:main
from
jakirkham-feedstocks:close_cuda118
Jan 11, 2024
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
This file was deleted.
Oops, something went wrong.
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
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.
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.
When applying these changes to feedstocks with the CUDA 12.0 migrator, found that re-rendering would error due to the
orderingnot including 11.8. So have added it hereHowever this means feedstocks would run into this issue as well. With these changes they would need to refresh the CUDA 12.0 migrator. Alternatively we could restart this migrator to ensure the new YAML is added. Though that feels like unnecessary extra effort for maintainers. Not sure if there are better options
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.
If you update it here in the pinning repo, every feedstock that has
.ci_support/migrations/cuda120.yamlwill use that updated variant unless they setuse_local: true. No need to restart anything.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.
If the feedstocks automatically pick up this change, great!
Had the impression that was not the case, but would be happy to be wrong
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.
Yep you are right
Confirmed by testing this locally with
conda-smithy's--exclusive-config-fileflagThere 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.
Have since done a few re-renders on feedstocks with both the CUDA 11.8 & 12 migrator included without issues
For the
use_local: truecase, searched through the feedstocks and found a handful that were affected. Submitted PRs to them to refresh their CUDA 12 migrators so that re-render works. Added some background in the PRs for contextThere 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.
Since the
use_local: trueworkaround was added by feedstocks working around a CUDA 12 + GCC 12 + pybind11 bug ( pybind/pybind11#4606 ), pybind11 made a fix ( pybind/pybind11@3414c56 ), which was released inpybind11version2.12.0. Coincidentally the same version that included the NumPy 2 fixes that we also need ( pybind/pybind11@705efcc ). This newer version ofpybind11was packaged in conda-forge earlier this year ( conda-forge/pybind11-feedstock#94 ). So for feedstocks usingpybind11directly, simply getting the latest version in conda-forge was sufficient for them to drop these workaroundsHowever the other issue we had was feedstocks that use PyTorch got
pybind11from a vendored copy in PyTorch (not the package). This comes up when a package#includes PyTorch's headers. Fortunately PyTorch upgraded its version of pybind11 to 2.12.0 as part of their NumPy 2 upgrade effort ( pytorch/pytorch@6c2f36c ). This was released in PyTorch version 2.4.0, which was recently packaged in conda-forge ( conda-forge/pytorch-cpu-feedstock#250 ). This allowed the remaining workarounds to be droppedWhile some of these workarounds were removed organically over time, a few were still around recently. So have worked with maintainers to clean these out. At this point, I see none of the original vendored CUDA 12 migrators
There are other cases where the CUDA 12 migrator is vendored. However this is usually done in packages where they build against the latest CUDA 12 and can continue to support older CUDA 12's. So this is irrelevant in this context
Mentioning here as the other context is in this thread or xref'd below. So this seemed like the natural place to include this information
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.
I think you're commenting on the wrong PR...?
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.
The comment relates to both PRs, but felt more natural here given more relevant context here
Also wanted to reference it in the other PR as done in comment: #6263 (comment)
Assuming that was the PR you had in mind