Repository navigation
Pin the CUDA build to Ubuntu 24.04 - #75
Merged
Merged
Conversation
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.
What this changes
The CUDA build job runs on
ubuntu-24.04instead ofubuntu-latest.Why
ubuntu-latestnow resolves to 26.04. The toolkit action follows the image and asks NVIDIA'subuntu2604repository forcuda-13-2, which is not published there yet, so every CUDA build job fails before compiling anything (first seen on #72, which only touchessrc/data). The release workflow already pins its CUDA build to a fixed Ubuntu version for the same kind of reason.How it was verified
cargo testpassescargo clippy --all-targets -- -D warningsis cleancuda_parityon a GPU--releaseWorkflow only. This PR's own CUDA build job is the test.
Checklist
tensor/opsandautograd/opsstill mirror each other///docs