Skip to content
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

Update to CCCL 2.7.0 #115

Closed
bdice opened this issue Oct 31, 2024 · 3 comments
Closed

Update to CCCL 2.7.0 #115

bdice opened this issue Oct 31, 2024 · 3 comments
Assignees

Comments

@bdice
Copy link
Contributor

bdice commented Oct 31, 2024

This issue tracks the progress of updating RAPIDS to CCCL 2.7.0. The current release candidate is v2.7.0-rc2.

@bdice
Copy link
Contributor Author

bdice commented Dec 3, 2024

I updated all the repositories above with the latest branch-25.02, and built and ran C++ and Python tests for every library manually [still finalizing cuGraph tests at this moment, will update when complete]. Testing locally is easier than running proper CI builds because we'd have to use upstream artifacts from every other library. Given that my local tests are looking good and CI is passing in the CCCL repo with RAPIDS 25.02 (NVIDIA/cccl#2967), I think we can safely move forward here.

These PRs are ready for review and/or could use an extra eye.

Once those two PRs are approved, I think we'll be ready to merge CCCL 2.7.0-rc2 in rapids-cmake, then revert the testing changes in cuDF and merge that. No other PRs have material changes that we need to merge, and the rest can be closed.

AyodeAwe pushed a commit to rapidsai/cudf that referenced this issue Dec 4, 2024
This PR updates to CCCL 2.7.0-rc2. Do not merge until all of RAPIDS is
ready to update.

Depends on rapidsai/rapids-cmake#710 and should
be admin-merged immediately after that PR.

Part of rapidsai/build-planning#115.

---------

Co-authored-by: Michael Schellenberger Costa <[email protected]>
@vyasr
Copy link
Contributor

vyasr commented Dec 10, 2024

@bdice can we close this now? The cuml issue seems like an edge case (whatever is happening there) and not worth keeping this open for.

@bdice bdice closed this as completed Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants