Skip to content

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

Closed
wants to merge 11 commits into from
Closed

Clean-up warnings from tests #13262

wants to merge 11 commits into from

Conversation

maikia
Copy link
Contributor

@maikia maikia commented Feb 25, 2019

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?

@jnothman
Copy link
Member

@maikia, is this PR meant to be doing more than ignoring SparseEfficiencyWarning? I'm wondering whether you have extra commits from other work here.

Copy link
Member

@jnothman jnothman left a 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

@jorisvandenbossche jorisvandenbossche changed the title Warnings in tests Clean-up warnings from tests Feb 27, 2019
@amueller
Copy link
Member

amueller commented Aug 6, 2019

Are you still working on this? Is this still relevant?

Base automatically changed from master to main January 22, 2021 10:50
@cmarmo cmarmo added the Needs Decision - Close Requires decision for closing label Sep 21, 2022
@cmarmo
Copy link
Contributor

cmarmo commented Sep 21, 2022

A lot of things have changed since this pull request, but there are still warnings in the tests (in particular I have checked 34 scipy.sparse.SparseEfficiencyWarning).
Should we close this PR and keep track of the different warnings in meta-issues like #4780? Thanks!

@thomasjpfan
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants