-
-
Notifications
You must be signed in to change notification settings - Fork 26.2k
Clean-up warnings from tests #13262
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
Clean-up warnings from tests #13262
Conversation
@maikia, is this PR meant to be doing more than ignoring SparseEfficiencyWarning? I'm wondering whether you have extra commits from other work here. |
…for untreated warnings
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.
Let us know when you need help / if this is ready for review
…est where it tests for alpha too small
…n warning in setup
Are you still working on this? Is this still relevant? |
A lot of things have changed since this pull request, but there are still warnings in the tests (in particular I have checked 34 |
Given the many changes, I'll say to close this one and have multiple PRs that resolves warnings one test at a time. Sometimes resolving the warning can be quite involved which calls for a single PR to fix each test. @maikia Thank you again for working on this issue. |
There are a lot of warnings generated during testing. Some of them might be ignored but some might be more important. Here I add ignore to the SparseEfficiencyWarning in test_validation
Reference Issues/PRs
What does this implement/fix? Explain your changes.
Any other comments?