-
Notifications
You must be signed in to change notification settings - Fork 912
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
[REVIEW] Fix getattr logic in GroupBy #5578
[REVIEW] Fix getattr logic in GroupBy #5578
Conversation
Please update the changelog in order to start CI tests. View the gpuCI docs here. |
def test_groupby_attribute_error(): | ||
err_msg = "Test error message" | ||
|
||
class TestGroupBy(cudf.core.groupby.GroupBy): |
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.
We're depending on some internals of groupby in this test. I don't like it but couldn't figure out a better solution
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.
By internals are you just referring to cudf.core.groupby.GroupBy
?
rerun tests |
Codecov Report
@@ Coverage Diff @@
## branch-0.15 #5578 +/- ##
===============================================
- Coverage 88.65% 85.86% -2.79%
===============================================
Files 57 72 +15
Lines 10945 12172 +1227
===============================================
+ Hits 9703 10452 +749
- Misses 1242 1720 +478
Continue to review full report at Codecov.
|
Noticed that our logic for
getattr
in GroupBy could lead to misleading error messages when anAttributeError
is raised within anyproperty
s in GroupBy. See encode/django-rest-framework#2108 for a description of the problem.