Skip to content
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

Forward-merge branch-24.02 to branch-24.04 #696

Merged
merged 1 commit into from
Jan 30, 2024
Merged

Conversation

GPUtester
Copy link
Contributor

Forward-merge triggered by push to branch-24.02 that creates a PR to keep branch-24.04 up-to-date. If this PR is unable to be immediately merged due to conflicts, it will remain open for the team to manually merge.

We observed that some CUDA packages were being pulled from the `nvidia` channel here: https://github.com/rapidsai/docker/actions/runs/7709797316/job/21011757079#step:9:552

I found that removing `cuda-python` changes the solver behavior in a way that satisfies our needs.

I also removed `cudatoolkit` because that is a transitive dependency of RAPIDS libraries, and only needed for CUDA 11. It is not needed at the top level `rapids` metapackage. Like `cuda-python`, it is constrained by `cuda-version`, so I think it's better to cut it.

Details:

The explicit dependency `rapids -> cuda-python`  is forcing the solver to prefer newer `cuda-python` versions, which in turn makes `cuda-version=12.0` ineffective at constraining `cuda-cudart`. The solver prefers to take `cuda-python 12.3` from conda-forge, but it also has to have `cuda-version 12.0` per our constraints (`cuda-python 12.3` requires `cuda-cudart>=12.3.101,<13.0a0` and `cuda-version>=12.0,<13.0a0`). So then we get `nvidia` channel packages (which are not constrained by `cuda-version`) of `cuda-cudart 12.3` to satisfy `cuda-python 12.3` rather than install `cuda-python 12.0` and get `cuda-cudart` from conda-forge.

Authors:
  - Bradley Dice (https://github.com/bdice)

Approvers:
  - Ray Douglass (https://github.com/raydouglass)

URL: #695
@GPUtester GPUtester requested a review from a team as a code owner January 30, 2024 22:31
@GPUtester GPUtester merged commit 6783123 into branch-24.04 Jan 30, 2024
10 checks passed
@GPUtester
Copy link
Contributor Author

SUCCESS - forward-merge complete.

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.

2 participants