DNM: Test CUDA 13.0 migrator#35
Conversation
…nda-forge-pinning 2025.08.11.12.28.22
|
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 ( I do have some suggestions for making it better though... For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/17445529106. Examine the logs at this URL for more detail. |
|
@billysuh7 @jakirkham It seems that the new runtime library path for CUDA 13 windows libraries is not setup correctly because the conda link-checker cannot find them. For context, the CUDA 12 build of this recipe dynamically links to both cufft and cudart, but fails to do so with CUDA 13. |
|
I added |
…nda-forge-pinning 2025.08.21.20.21.31
|
I have rerender this PR to use the cuda120_dev channel, but the packages might not be there yet. Please restart the CI if the Windows build fails again. |
|
Great! It works. |
Checklist
0(if the version changed)conda-smithy(Use the phrase@conda-forge-admin, please rerenderin a comment in this PR for automated rerendering)