-
Notifications
You must be signed in to change notification settings - Fork 54
Use rapidsai/sccache in CI
#674
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
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. |
|
/ok to test 2f01dd6 |
Greptile SummaryThis PR switches from Mozilla's sccache to the RAPIDS fork to enable caching for CUDA fatbin and ltoir compilation outputs. The changes properly configure the RAPIDS sccache binary installation, enable preprocessor cache mode for better caching, and update the Makefile to use sccache for previously excluded compilation targets (fatbin and ltoir). The environment variable configuration has been updated to use GHA cache backend instead of disk-based caching.
Confidence Score: 5/5
Important Files Changed
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Additional Comments (1)
-
testing/Makefile, line 34 (link)style: Outdated comment - the RapidsAI fork now supports fatbin and ltoir
2 files reviewed, 1 comment
|
/ok to test 3c9bde4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Additional Comments (1)
-
testing/Makefile, line 34 (link)syntax: outdated comment -
rapidsai/sccachenow supports fatbin and ltoir
2 files reviewed, 1 comment
|
/ok to test 24a7700 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Additional Comments (2)
-
.github/workflows/build-wheel.yml, line 50 (link)style: using
/releases/latest/could lead to unexpected behavior if the latest release introduces breaking changes -
.github/workflows/build-wheel.yml, line 102-110 (link)style: removed
SCCACHE_DIRandSCCACHE_CACHE_SIZEenv vars from the cibuildwheel environmentThe
ci/tools/env-varsscript still sets these inGITHUB_ENV(lines 40-41), but they're no longer passed to the cibuildwheel container. Verifysccachewill use defaults or if these need to be passed through.
2 files reviewed, 2 comments
|
/ok to test e7d29c0 |
|
/ok to test b1760f2 |
aaf40ba to
e5e6799
Compare
|
/ok to test e5e6799 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Additional Comments (2)
-
.github/workflows/build-wheel.yml, line 50-51 (link)syntax: Remove the second
-xflag before the wildcard pattern. The-xis already specified in-xvzf, and the second one is invalid syntax. -
.github/workflows/build-wheel.yml, line 166-167 (link)syntax: Same issue: remove the second
-xflag before the wildcard pattern.
3 files reviewed, 2 comments
|
/ok to test 95962f5 |
95962f5 to
d74dc10
Compare
|
/ok to test d74dc10 |
cpcloud
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
- Add arch specific target support (NVIDIA#549) - chore: disable `locked` flag to bypass prefix-dev/pixi#5256 (NVIDIA#714) - ci: relock pixi (NVIDIA#712) - ci: remove redundant conda build in ci (NVIDIA#711) - chore(deps): bump numba-cuda version and relock pixi (NVIDIA#707) - Dropping bits in the old CI & Propagating recent changes from cuda-python (NVIDIA#683) - Fix `test_wheel_deps_wheels.sh` to actually uninstall `nvvm` and `nvrtc` packages for CUDA 13 (NVIDIA#701) - perf: remove some exception control flow and buffer-exception penalization for arrays (NVIDIA#700) - perf: let CAI fall through instead of calling from_cuda_array_interface (NVIDIA#694) - chore: perf lint (NVIDIA#697) - chore(deps): bump deps in pixi lockfile (NVIDIA#693) - fix: use freethreading-supported `_PySet_NextItemRef` where possible (NVIDIA#682) - Support python `3.14` (NVIDIA#599) - Remove customized address space tracking and address class emission in debug info (NVIDIA#669) - Drop `experimental` from cuda.core namespace imports (NVIDIA#676) - Remove dangling references to NUMBA_CUDA_ENABLE_MINOR_VERSION_COMPATIBILITY (NVIDIA#675) - Use `rapidsai/sccache` in CI (NVIDIA#674) - chore(dev-deps): remove ipython and pyinstrument (NVIDIA#670) - Set up a new VM-based CI infrastructure (NVIDIA#604)
- Add arch specific target support (#549) - chore: disable `locked` flag to bypass prefix-dev/pixi#5256 (#714) - ci: relock pixi (#712) - ci: remove redundant conda build in ci (#711) - chore(deps): bump numba-cuda version and relock pixi (#707) - Dropping bits in the old CI & Propagating recent changes from cuda-python (#683) - Fix `test_wheel_deps_wheels.sh` to actually uninstall `nvvm` and `nvrtc` packages for CUDA 13 (#701) - perf: remove some exception control flow and buffer-exception penalization for arrays (#700) - perf: let CAI fall through instead of calling from_cuda_array_interface (#694) - chore: perf lint (#697) - chore(deps): bump deps in pixi lockfile (#693) - fix: use freethreading-supported `_PySet_NextItemRef` where possible (#682) - Support python `3.14` (#599) - Remove customized address space tracking and address class emission in debug info (#669) - Drop `experimental` from cuda.core namespace imports (#676) - Remove dangling references to NUMBA_CUDA_ENABLE_MINOR_VERSION_COMPATIBILITY (#675) - Use `rapidsai/sccache` in CI (#674) - chore(dev-deps): remove ipython and pyinstrument (#670) - Set up a new VM-based CI infrastructure (#604)
Use the
rapidsai/sccachefork in CI because it supports caching fatbins and ltoir.Closes #673