[DO NOT MERGE] Test NVIDIA's official CUDA packages#143
[DO NOT MERGE] Test NVIDIA's official CUDA packages#143leofang wants to merge 18 commits intoconda-forge:mainfrom
Conversation
MNT: Re-rendered with conda-build 3.21.4, conda-smithy 3.12, and conda-forge-pinning 2021.08.14.10.30.44
|
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 ( |
MNT: Re-rendered with conda-build 3.21.4, conda-smithy 3.12, and conda-forge-pinning 2021.08.14.10.30.44
|
@conda-forge-admin, please rerender |
…a-forge-pinning 2021.08.14.10.30.44
MNT: Re-rendered with conda-build 3.21.4, conda-smithy 3.12, and conda-forge-pinning 2021.08.19.19.17.07
MNT: Re-rendered with conda-build 3.21.4, conda-smithy 3.12, and conda-forge-pinning 2021.08.19.19.17.07
|
|
|
Darn it, I was fooled by the ongoing Azure issue. The feedstock status is not reported, so the green check only includes the linter's report... |
|
FYI Azure status issue has been fixed |
| - cuda-nvcc # for crt/host_defines.h | ||
| - cuda-cudart | ||
| - cuda-nvrtc | ||
| - cuda-nvprof # for cuda_profiler_api.h |
There was a problem hiding this comment.
If we have the cuda-profiler-api package, does that solve this need? Or are there other things that cuda-nvprof is still needed for?
There was a problem hiding this comment.
I think CuPy doesn't need the legacy nvprof (cmdline tool), just the profiler header.
|
Would be superseded by #199. |
Close #139.
Checklist
0(if the version changed)conda-smithy(Use the phrase@conda-forge-admin, please rerenderin a comment in this PR for automated rerendering)