Repository navigation
Conversation
Install mozilla/sccache v0.18.0 (checksum-verified) in build-wheel.yml instead of the rapidsai fork, and pin the same version in test-sdist-linux.yml. Remove ACTIONS_CACHE_URL and ACTIONS_RUNTIME_URL, which sccache's GHA v2 cache backend does not read, and drop the now-redundant github-script step in test-sdist-linux.yml.
Contributor
…IONS_ vars Install sccache with mozilla-actions/sccache-action (pinned to v0.18.0) in build-wheel.yml and test-sdist-linux.yml instead of the rapidsai fork, and remove the custom install and github-script steps. Drop ACTIONS_CACHE_URL and ACTIONS_RUNTIME_URL, which the GHA v2 cache backend does not read.
Contributor
Author
|
/ok to test 235faa3 |
Member
Contributor
|
Member
|
@juenglin Yeah, let me know if you have any issues. Mozilla's fork isn't sound for caching CUDA files, and ours has a number of other major improvements (like sharing the preprocessor cache). Also, it's about to get an order of magnitude faster than Mozilla's for caching all compilation types (and will be able to cache non-compilation steps, like linking, too). |
This branch has not been deployed
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
3 participants
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.
Description
Use mozilla/sccache v0.18.0 in both workflows that use sccache, and remove the
ACTIONS_*variables that sccache doesn't read.Why drop the rapidsai fork
build-wheel.ymlhas installedrapidsai/sccachesince #1914. The stated reason there was thatmozilla-actions/sccache-actionhadn't been updated since Oct 2025. That is no longer true (v0.0.11 was released 2026-07-29), and the history doesn't mention any other reason.Nothing cuda-python builds uses what the fork adds. The fork is based on mozilla's v0.18.0 (
v0.18.0-rapids.6) and adds mostly CUDA toolchain caching (nvccsub-tool handling forcudafe++,cicc,ptxas) and distributed-compile work. Our CI doesn't use those:.cusources incuda_bindings,cuda_coreorcuda_pathfinder. The only.cufile is the test binarycuda_core/tests/test_binaries/saxpy.cu.Build linux-64, CUDA 13.4.2 / py3.10) show onlyc++ [gcc]compiles. There are noCUDA,PTXorCUBINentries.--show-adv-statsand--show-stats --stats-format=json(used by.github/actions/sccache-summary) exist in mozilla's sccache.Changes
build-wheel.yml: replace thecurlinstall of the rapidsai fork and thegithub-scriptstep withmozilla-actions/sccache-action(pinned to the v0.0.11 SHA) withversion: v0.18.0anddisable_annotations: 'true'. The action downloads and checksum-verifies the binary and exports the cache variables. Stats are still reported from inside the cibuildwheel container, so the action's host-side reporting is turned off.test-sdist-linux.yml: pin the action toversion: v0.18.0and remove thegithub-scriptstep. It only re-exported the two obsolete variables.ACTIONS_CACHE_URLandACTIONS_RUNTIME_URL: sccache's GitHub Actions cache backend (OpenDALghac) does not readACTIONS_RUNTIME_URLat all, and readsACTIONS_CACHE_URLonly when the v1 cache service is in use. WithACTIONS_CACHE_SERVICE_V2set, as it is here, onlyACTIONS_RESULTS_URLandACTIONS_RUNTIME_TOKENare used. That is also what sccache's owndocs/GHA.mdlists.ACTIONS_CACHE_SERVICE_V2,ACTIONS_RESULTS_URLandACTIONS_RUNTIME_TOKEN. The container doesn't get them from the runner otherwise.Benefits
version:input in each workflow.How to review
Compare the sccache stats in the
Build linux-*jobs with the earlier run linked above (cache hit rate andCache hits (c++ [gcc])). Also check that thesccache-summarytable still renders.Checklist