Dropping bits in the old CI & Propagating recent changes from cuda-python#683
Dropping bits in the old CI & Propagating recent changes from cuda-python#683leofang merged 10 commits intoNVIDIA:mainfrom
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
11b8f13 to
39bf323
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
5fcd89c to
d58a07a
Compare
This comment was marked as outdated.
This comment was marked as outdated.
d58a07a to
d800591
Compare
This comment was marked as outdated.
This comment was marked as outdated.
d800591 to
3b20f0a
Compare
3b20f0a to
03b7b49
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
e177af1 to
78aad77
Compare
|
/ok to test 78aad77 |
This comment was marked as outdated.
This comment was marked as outdated.
0d5e440 to
78aad77
Compare
Greptile SummaryThis PR successfully consolidates the CI infrastructure by migrating all jobs from legacy workflows ( Key changes:
The consolidation maintains all existing functionality while simplifying CI management and reducing redundancy between parallel CI systems. Confidence Score: 5/5
Important Files Changed
|
There was a problem hiding this comment.
Additional Comments (1)
-
.github/workflows/ci-new.yaml, line 346 (link)style: leftover commented code from debugging or development
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
23 files reviewed, 1 comment
Greptile's behavior is changing!From now on, if a review finishes with no comments, we will not post an additional "statistics" comment to confirm that our review found nothing to comment on. However, you can confirm that we reviewed your changes in the status check section. This feature can be toggled off in your Code Review Settings by deselecting "Create a status check for each PR". |
|
/ok to test d5b8b63 |
|
@kkraus14 @rparolin @gmarkall this needs to be done before we can merge this PR: #683 (comment). I don't have admin access to this repo, so I can't do it myself 😛 |
Keith granted me access to the devop group, and I was able to adjust the ruleset to merge this PR. |
- 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)

Part of #671.
This PR removes the old wheel build/test workflows in favor of the new ones. In particular, this allows us to drop the GH-hosted Windows GPU runners (
cuda-python-windows-gpu-github) entirely and to also reduce the amount of CI resource that we use in this repo (we currently use more than we should, because the old/new CIs are running in parallel).Then, all other test jobs, such as conda & 3rd libs, in the old CI (
ci.yamlruns onmain, whilepr.yamlruns per PR, but the content of both are almost identical) are hooked to the new CI as-is (ci-new.yamlruns on bothmainand per-PR). Further consolidation would require some nontrivial changes (ex: commit 0d5e440 proved that we still need to use RAPIDS containers for these jobs, so I reverted it).Some recent cuda-python CI changes are propagated to here, including transition from JSON to YAML files. However, the two YAML files
test-matrix.yamlandmatrix.yamlstill cannot be merged yet, due to some workflows still using the latter (ex: #680).Below is an LLM-generated summary:
➡️ CLICK ME ⬅️
This pull request significantly refactors and consolidates the project's CI/CD workflows. The main focus is on migrating jobs from legacy workflow files (
ci.yaml,pr.yaml) into the unifiedci-new.yamlworkflow, modernizing configuration files, and improving maintainability by removing redundancy and unused scripts.CI/CD Workflow Consolidation and Refactoring:
Migrated all major jobs (e.g.,
pre-commit, matrix computation, conda/wheel builds and tests, third-party integration tests, documentation, and coverage reporting) from the old.github/workflows/ci.yamland.github/workflows/pr.yamlfiles into.github/workflows/ci-new.yaml, and then deleted the legacy workflow files. This centralizes and simplifies CI management. [1] [2] [3] [4] [5]Updated the test matrix logic in
.github/workflows/test-wheel-linux.ymlto use YAML files andyqfor matrix generation instead of JSON andjq, aligning with the new workflow structure.Configuration and Quality-of-Life Improvements:
Enhanced
.github/dependabot.ymlwith improved copyright, scheduling, and update grouping, and expanded update types to include major version bumps.Improved CUDA version extraction in
.github/workflows/ci-new.yamlto useyqwith YAML files instead ofjqwith JSON, reflecting the project's move to YAML-based configuration.Cleanup and Maintenance:
Bug Fixes and Minor Adjustments:
fetch_ctkaction to only move thelibdirectory if it exists, preventing errors on certain platforms.