Skip to content

DNM: Test CUDA 13.0 migrator#35

Closed
carterbox wants to merge 12 commits into
conda-forge:mainfrom
carterbox:test-cuda-13.0-migrator
Closed

DNM: Test CUDA 13.0 migrator#35
carterbox wants to merge 12 commits into
conda-forge:mainfrom
carterbox:test-cuda-13.0-migrator

Conversation

@carterbox

Copy link
Copy Markdown
Member

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

@conda-forge-admin

conda-forge-admin commented Aug 12, 2025

Copy link
Copy Markdown
Contributor

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 (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-forge-tick (the bot). Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.
  • ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.

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.

@carterbox

Copy link
Copy Markdown
Member Author

@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.

@carterbox

Copy link
Copy Markdown
Member Author

I added --verbose to the logs. There is no mention of cudart_static.lib, so I don't see why libastra with CUDA 13 is linking statically to cudart.

@carterbox

Copy link
Copy Markdown
Member Author

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.

@carterbox

Copy link
Copy Markdown
Member Author

Great! It works.

@carterbox carterbox closed this Sep 5, 2025
@carterbox carterbox mentioned this pull request Sep 16, 2025
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