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

[TEST] Test cuSpatial with artifacts from rapidsai/rmm#1095 #1294

Closed

Conversation

harrism
Copy link
Member

@harrism harrism commented Nov 9, 2023

Test cuSpatial with changes from rapidsai/rmm#1095

Description

Checklist

  • I am familiar with the Contributing Guidelines.
  • New or existing tests cover these changes.
  • The documentation is up to date with these changes.

@harrism harrism added feature request New feature or request DO NOT MERGE Hold off on merging; see PR for details non-breaking Non-breaking change labels Nov 9, 2023
@harrism harrism self-assigned this Nov 9, 2023
@github-actions github-actions bot added the ci label Nov 9, 2023
@github-actions github-actions bot added the Python Related to Python code label Nov 13, 2023
@@ -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([]))
Copy link
Contributor

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.

Copy link
Member Author

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?

Copy link
Contributor

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.

@bdice bdice closed this Nov 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci DO NOT MERGE Hold off on merging; see PR for details feature request New feature or request non-breaking Non-breaking change Python Related to Python code
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants