-
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 FutureWarnings and DeprecationWarnings as errors in cugraph #4415
Enable FutureWarnings and DeprecationWarnings as errors in cugraph #4415
Conversation
…deprwarnings/errors
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.
Thanks! We may be able to remove some of the features that have exceeded the deprecation grace period and make this list smaller in a future PR.
Sorry for the delay. Finally got the CI to green |
I'm currently investigating the |
/merge |
Supersedes #4271
There are some tests and internal usages of APIs that emit these warnings still. I don't know the best way to handle these warnings, but this PR ensures that new
FutureWarning
s andDeprecationWarning
s will raise an error in the CI