-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Support CUDA 12 #199
Support CUDA 12 #199
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
…nda-forge-pinning 2023.04.18.01.55.25
disable aarch64/ppc64le for now
This comment was marked as resolved.
This comment was marked as resolved.
…nda-forge-pinning 2023.04.18.01.55.25
This comment was marked as outdated.
This comment was marked as outdated.
Co-authored-by: jakirkham <[email protected]>
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do. This message was generated by GitHub actions workflow run https://github.com/conda-forge/cupy-feedstock/actions/runs/5136254960. |
As this appears to no longer be needed, try dropping it.
@conda-forge-admin, please re-render |
…nda-forge-pinning 2023.05.31.19.00.54
Looks like VS2019 still doesn't work here. So readd the `conda_build_config.yaml` with a configuration to use VS2017 on Windows again.
@conda-forge-admin, please re-render |
…nda-forge-pinning 2023.05.31.19.00.54
Thanks, John, let's merge. I noticed one of the ppc64le CIs started hitting error since yesterday. I hope it's just a transient issue. Will monitor & retry on master. |
btw I deleted the |
@kmaehashi To reduce potential conflicts, would it be OK if I upstream the patch I wrote here? It should be no-op for normal users, and only triggered in a conda-build environment. |
Thanks Leo! 🙏 |
Travis is misbehaving again... (no output in 10 mins) Will switch back to cross compiling. |
See #202. |
FWIW tried a new Travis build to see if it was a fluke. Though happy to go with cross-compilation |
Oh I already retried twice, sorry I forgot to mention. |
Ah ok. Yeah cross-compilation seems like the right solution then |
Yes of course 😄 |
Sent a PR: cupy/cupy#7603 🙂 |
# TODO: see https://github.com/conda-forge/cudnn-feedstock/issues/58 | ||
- cudnn >=8 # [not ((aarch64 or ppc64le) and cuda_compiler_version == "12.0")] | ||
# TODO: wait for NCCL to catch up | ||
- nccl >=2.8 # [linux and cuda_compiler_version != "12.0"] | ||
- cutensor >=1.4,<2 | ||
- cusparselt 0.2.0.* # [(linux64 or win) and cuda_compiler_version == "11.2"] |
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.
Wonder if we can drop some of these selectors now that these packages have been rebuilt
Edit: Filed as issue ( #207 )
Close #139. Close #143.
Hi! This is the friendly automated conda-forge-webservice.
I've rerendered the recipe as instructed in #198.
Here's a checklist to do before merging.
Fixes #198