Closed
Conversation
…penstack-cpu-xlarge using Cirun
…nda-forge-pinning 2025.05.20.06.20.57
CUDA 12.8 added support for architectures `sm_100`, `sm_101` and `sm_120`, while CUDA 12.9 further added `sm_103` and `sm_121`. To build for these, maintainers will need to modify their existing list of specified architectures (e.g. `CMAKE_CUDA_ARCHITECTURES`, `TORCH_CUDA_ARCH_LIST`, etc.) for their package. A good balance between broad support and storage footprint (resp. compilation time) is to add `sm_100` and `sm_120`. Since CUDA 12.8, the conda-forge nvcc package now sets `CUDAARCHS` and `TORCH_CUDA_ARCH_LIST` in its activation script to a string containing all of the supported real architectures plus the virtual architecture of the latest. Recipes for packages who use these variables to control their build but do not want to build for all supported architectures will need to override these variables in their build script. ref: https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html#new-features
…5.08.31.03.07.54 Other tools: - conda-build 25.7.0 - rattler-build 0.46.0 - rattler-build-conda-compat 1.4.5
…5.09.25.19.16.51 Other tools: - conda-build 25.7.0 - rattler-build 0.47.0 - rattler-build-conda-compat 1.4.6
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 ( 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/19008245763. Examine the logs at this URL for more detail. |
Member
|
@cbourjau, there seem to have been some changes w.r.t. the cuda setup. Nothing impossible to fix I imagine. I don't know when I'll get to look at this more closely, if you have some cycles to try to fix it that would be great! |
Co-Authored-By: H. Vetinari <h.vetinari@gmx.com>
Conda-forge assumed cudnn 9.x builds would stay compatible with each other. This is the case for the API/ABI of the library, but nvidia dropped support for older GPU architectures in cudnn 9.11. Since we have no package-level metadata about compatibility with specific GPU architectures, this effectively breaks all packages built atop cudnn for users on affected older GPUs. In order to remedy this situation, we need to rebuild all cudnn-dependent feedstocks against cudnn 9.10 (the last version with full architecture support), before we mark all those newer cudnn builds as broken. This only affects artefacts for CUDA 12.x; those for CUDA 13.x are not affected, since CUDA 13 never supported those older architectures in the first place. For more details see: conda-forge/cudnn-feedstock#124
…5.11.01.15.03.42 Other tools: - conda-build 25.9.0 - rattler-build 0.48.1 - rattler-build-conda-compat 1.4.9
h-vetinari
force-pushed
the
cirun-with-1.23.1
branch
from
2f26a15 to
eee5dac
Compare
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Unfortunately, we still see some test failures for Windows in #149 . This PR is a work-in-progress attempt to see if those issues might vanish if we target the latest version.
Closes #149
Closes #150
Closes #151
Closes #152
Closes #153
Closes #155
Closes #158