ci(qdp): build the extension once and reuse it across the test matrix - #1413
Closed
ryankert01 wants to merge 1 commit into
Closed
ci(qdp): build the extension once and reuse it across the test matrix#1413ryankert01 wants to merge 1 commit into
ryankert01 wants to merge 1 commit into
Conversation
The Python Testing workflow rebuilt the QDP extension independently in every matrix leg (3.10/3.11/3.12). Add a single `build` job that compiles the CPU/no-CUDA stub wheels for all supported interpreters once, uploads them as an artifact, and have the test matrix download and install the matching wheel instead of recompiling. QDP_NO_CUDA=1 makes the stub build explicit, matching the prior per-leg behaviour (which fell back to stubs because nvcc is absent on the runner). This removes the duplicated compilation across the matrix; the heavy non-pyo3 crates now compile a single time.
Member
Author
|
Not effective |
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
1 participant
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.
Related Issues
Changes
Why
The Python Testing workflow rebuilt the QDP extension independently in every
matrix leg (3.10 / 3.11 / 3.12), compiling the same Rust code three times. The
legs run in parallel, so this duplicated CI compute (billed minutes) without
buying any wall-clock speedup.
How
buildjob that compiles the CPU / no-CUDA stub wheels for allsupported interpreters once and uploads them as an artifact.
testmatrix toneeds: build: it downloads the artifact andinstalls the wheel matching each leg's interpreter instead of recompiling.
QDP_NO_CUDA=1makes the stub build explicit, matching the prior per-legbehaviour (which fell back to stubs because
nvccis absent on the runner —see
qdp/qdp-core/build.rsandqdp/qdp-kernels/build.rs).Net effect: the heavy non-pyo3 crates compile a single time instead of once per
leg. The
rust-checkgate, the test environment setup, and thepytestinvocation are otherwise unchanged. The CUDA wheel build in
wheel-build.yml(used for distribution) is intentionally left as-is.
Job graph:
rust-check → build → test (matrix).Checklist