-
Notifications
You must be signed in to change notification settings - Fork 15
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
Updating numpy creates a different number of warnings...which fails CI #1144
Comments
Welp, I updated my entire conda env and am still not able to reproduce these errors. If they still persist after we resolve #1143 I am willing to dig deeper, but let's try fixing that and recreating the dependabot PR before burning a bunch of time on this. |
We could export the conda environment to recreate the exactly same environment. Also, did you check if we warn on more things in the CI? |
Derp. Yes, of course. So the warnings are not easy to correlate with the tests in the output, so I can't easily tell which ones are the extra warnings being counted in these tests. However, I find the following suspicious candidates introduced with numpy 1.25.0:
What I find weird about this is that I thought maybe that
On both the For h5io we are already on the most recent release 1.7.0. There have been modifications to the problematic file, but when I compare the relevant chunk of code for 1.7.0 and main, they look identical. So here I don't know how or why it's throwing the warning to start with, and I don't see any reason to think updating will help. |
There is one "true" failure when updating numpy to 1.25 (#1140) discussed in #1143. The remaining failures are because we get more warnings than expected. I updated numpy on my local machine, but I guess the warnings are coming from some interplay between numpy and other packages because these tests all still pass fine on my machine.
The warning-counting-failures for reference:
The text was updated successfully, but these errors were encountered: