-
Notifications
You must be signed in to change notification settings - Fork 309
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
Enable pytest failures on warnings from cudf #4223
Enable pytest failures on warnings from cudf #4223
Conversation
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.
What is the schedule to merge this?
Is it for 24.04?
This is not critical for 24.04. Fine to de-prioritize over other PRs |
…t/warning_failure
…eschke/cugraph into tests/pytest/warning_failure
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.
Thank you very much!
We should have treated cudf warnings as test failures long ago.
All - can we get this is as soon as possible. while the warnings do not stop an analytic, is still looks bad on us to even have warrings |
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.
Looks great !!!
…t/warning_failure
…eschke/cugraph into tests/pytest/warning_failure
…t/warning_failure
…eschke/cugraph into tests/pytest/warning_failure
…t/warning_failure
/merge |
In 24.04, cudf issues a FutureWarning when using positional indexing with
__getitem__
. The change here is to useiloc
instead.Additionally the test suite will now fail when a warning comes from cudf as apart of rapidsai/build-planning#26