-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
8000
[TST] Upcoming dependency test failures #24060
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
Milestone
Comments
This does look real:
|
Is this something we should investigate for 3.6.1? The change becomes user-facing in existing versions of matplotlib when a new version of the responsible dependency gets released. If we need to fix this on our side, it is desirable to have a fixed version already out there to minimize user-impact. |
Add some floating point tolerances to these tests so they don't fail is probably OK. |
This was referenced Oct 8, 2022
This was referenced Oct 22, 2022
melissawm
pushed a commit
to melissawm/matplotlib
that referenced
this issue
Dec 19, 2022
This is similar to matplotlib#22132 in that NumPy has added more code paths that now take advantage of AVX512 optimizations and causes slight variations in results. Fixes matplotlib#24060
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The weekly build with nightly wheels from numpy and pandas
has failed. Check the logs for any updates that need to be
made in matplotlib.
https://github.com/matplotlib/matplotlib/actions/runs/3163174215
The text was updated successfully, but these errors were encountered: