-
Notifications
You must be signed in to change notification settings - Fork 47
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
CCCL 2.2.0 migration #502
Labels
Comments
bdice
added
feature request
New feature or request
? - Needs Triage
Need team to review and classify
labels
Dec 8, 2023
This was referenced Dec 18, 2023
rapids-bot bot
pushed a commit
that referenced
this issue
Dec 19, 2023
Something is going wrong in `thrust::copy`, so I am adding a patch to revert NVIDIA/cccl#211. This will fix the failing tests for rapidsai/cuspatial#1315. This is where it's failing, with `thrust::copy`: https://github.com/rapidsai/cuspatial/blob/8e8fa0689339c0288746b01a8af66fb599f5c770/cpp/tests/range/multipolygon_range_test.cu#L800 CI log: https://github.com/rapidsai/cuspatial/actions/runs/7229405991/job/19700477218?pr=1315#step:7:3280 ``` [ RUN ] MultipolygonRangeOneTest/1.OneMultipolygonRange unknown file: Failure C++ exception with description "__copy:: D->D: failed: cudaErrorInvalidValue: invalid argument" thrown in the test body. [ FAILED ] MultipolygonRangeOneTest/1.OneMultipolygonRange, where TypeParam = double (0 ms) ``` I traced it down to this CCCL PR - note that `thrust::transform(..., thrust::identity{})` works, but the new `thrust::copy` code path in NVIDIA/cccl#211 that calls `cudaMemcpyAsync` doesn't work for some reason. I was not able to identify the exact reason why that PR causes the failure. Patching this out will unblock RAPIDS and let us migrate forward with CCCL 2.2.0. This helps with #502. Authors: - Bradley Dice (https://github.com/bdice) Approvers: - Michael Schellenberger Costa (https://github.com/miscco) - Robert Maynard (https://github.com/robertmaynard) URL: #511
rapids-bot bot
pushed a commit
that referenced
this issue
Dec 19, 2023
Part of #502. This updates cuCollections for CCCL 2.2.0 support. This should be merged when the rest of RAPIDS is ready to update to CCCL 2.2.0, just before merging RMM and other library PRs. Authors: - Bradley Dice (https://github.com/bdice) Approvers: None URL: #510
I double-checked all the PRs linked above and we're ready to begin merging. Here is the order of operations and their dependencies in parentheses:
|
This migration is complete. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
This is a tracking issue for updates of RAPIDS to CCCL 2.2.0.
There are two phases: adding compatibility so that libraries can build with CCCL 2.2.0, and then actually doing the upgrade. I am opening separate PRs for each phase to minimize the diff that we have to keep in sync with ongoing library development.
High-Level Tasks
Some of this work is being done in parallel, following the RAPIDS dependency tree.
Then:
Compatibility
PRs adding compatibility with CCCL 2.2.0 (e.g. by adding
cuda::proclaim_return_type
around device lambdas):Version Updates
PRs updating to use
rapids_cpm_cccl
:The text was updated successfully, but these errors were encountered: