-
Notifications
You must be signed in to change notification settings - Fork 157
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
[TEST] Test cuSpatial with artifacts from rapidsai/rmm#1095 #1294
[TEST] Test cuSpatial with artifacts from rapidsai/rmm#1095 #1294
Conversation
@@ -14,7 +14,7 @@ def _test_hausdorff_from_list_of_spaces(spaces): | |||
def test_empty(): | |||
actual = _test_hausdorff_from_list_of_spaces([]) | |||
|
|||
expected = cudf.DataFrame([]) | |||
expected = cudf.DataFrame([], columns=cudf.Index([])) |
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.
Likely an upstream cuDF change made the empty Dataframe uses a RangeIndex
as the column names, instead of cudf.Index
. Since semantically both represent empty column names, I simply change the gold result here to let tests pass.
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.
OK thanks. Sounds like once everything is passing we will need to update this PR to remove the CI changes and get this fix merged in?
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.
I think that's right, otherwise we might have to handle this at release time.
…patial into test/cuspatial-test-rmm-1095
Test cuSpatial with changes from rapidsai/rmm#1095
Description
Checklist