fix(core): make pixi lock solve across CUDA variants#1758
Merged
cpcloud merged 2 commits intoNVIDIA:mainfrom Mar 12, 2026
Merged
fix(core): make pixi lock solve across CUDA variants#1758cpcloud merged 2 commits intoNVIDIA:mainfrom
cpcloud merged 2 commits intoNVIDIA:mainfrom
Conversation
Align the cuda-core and cuda-bindings Pixi source-package variants with the selected CUDA major and keep local checkout wiring out of the cu12 solve path. This restores cross-platform lock generation after the package and cuda-pathfinder version bumps changed the source metadata. Made-with: Cursor
Contributor
|
Auto-sync is disabled for ready for review pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
Regenerate the cuda-bindings lockfile so it matches the updated CUDA variant layout and remains reproducible alongside the core Pixi changes. Made-with: Cursor
Contributor
Author
|
/ok to test |
This comment has been minimized.
This comment has been minimized.
rparolin
approved these changes
Mar 12, 2026
|
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.
Summary
cuda-coreandcuda-bindingsPixi source-package metadata with the selected CUDA major by makingcuda-versiona build variant and propagating it through package host/run dependencieslocal-depsfeature sodefault,cu13, andexamplesstill use the localcuda_bindings/cuda_pathfindercheckouts whilecu12resolves against published packagescuda-coreto target-specific CUDA dev packages, scope the profiler header dependency to Linux, and give theexamplesenvironment its own CUDA system requirement so cross-platform solves stay consistentcuda_core/pixi.lockandcuda_bindings/pixi.lockso the manifests and committed lockfiles stay in syncWhy this is needed
cuda-core,cuda-bindings, andcuda-pathfinderforced Pixi to re-resolve the local path packagescuda-versionbuild variant, Pixi generated source metadata for the local packages against the wrong CUDA major, which madepixi lockfail or panic when it tried to solvecu12,cu13, andexamplesacross Linux and Windowswin-64How it works
cuda-versionis now part of the source-package build matrix, so Pixi can build and lock distinct CUDA 12 and CUDA 13 variants of the local packages instead of reusing mismatched metadatalocal-depsisolates the editable sibling-checkout workflow from the published-packagecu12workflow, which avoids forcing the localcuda-bindingscheckout through a CUDA 12 solve path it does not need for this repoexamplesfeature declares its own CUDA system requirement sopytorch-gpucan resolve its__cudavirtual package needs without reintroducing those constraints into the other environments__cudawhen the driver libraries are discoverable through the loader path; exportingLD_LIBRARY_PATH=/run/opengl-driver/libmakespixisee__cuda=13.2