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

[FEA] Smoke test for RAPIDS shuffle #989

Closed
jlowe opened this issue Oct 20, 2020 · 0 comments · Fixed by #1000
Closed

[FEA] Smoke test for RAPIDS shuffle #989

jlowe opened this issue Oct 20, 2020 · 0 comments · Fixed by #1000
Assignees
Labels
P1 Nice to have for release test Only impacts tests

Comments

@jlowe
Copy link
Member

jlowe commented Oct 20, 2020

Is your feature request related to a problem? Please describe.
#646 passing CI shows that we are lacking a basic smoke test of the RAPIDS shuffle that would catch cases where it cannot shuffle anything.

Describe the solution you'd like
At least one unit test should run with the RAPIDS shuffle enabled, probably in local mode to avoid the need for a full working UCX setup.

@jlowe jlowe added feature request New feature or request test Only impacts tests P1 Nice to have for release labels Oct 20, 2020
@jlowe jlowe self-assigned this Oct 20, 2020
@jlowe jlowe added this to the Oct 12 - Oct 23 milestone Oct 20, 2020
@sameerz sameerz removed the feature request New feature or request label Dec 14, 2020
tgravescs pushed a commit to tgravescs/spark-rapids that referenced this issue Nov 30, 2023
* Update gcc 11 to support both cuda 11 and 12 build

Signed-off-by: Peixin Li <pxli@nyu.edu>

* fix conflict CUDA_VERSION within cuda image

* add comment

* fix copyright

Signed-off-by: Peixin Li <pxli@nyu.edu>

* update cudf submodule to include gcc11 update

Signed-off-by: Peixin Li <pxli@nyu.edu>

---------

Signed-off-by: Peixin Li <pxli@nyu.edu>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 Nice to have for release test Only impacts tests
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants