-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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
CI: Unpin matplotlib #51990
CI: Unpin matplotlib #51990
Conversation
cc @mroeschke I think you took a closer look at the failures when 3.7 came out. Is this test failure expected and we have to fix it or is it on the matplotlib side? |
I don't remember seeing For |
#52150 fixes one of the errors. The other failure I think you should fix by making the data range bigger with your test data or add a warning filter to that test. |
# Conflicts: # ci/deps/actions-310.yaml # ci/deps/actions-311.yaml # ci/deps/actions-38-downstream_compat.yaml # ci/deps/actions-38.yaml # ci/deps/actions-39.yaml # ci/deps/circle-38-arm64.yaml # environment.yml # requirements-dev.txt
Owee, I'm MrMeeseeks, Look at me. There seem to be a conflict, please backport manually. Here are approximate instructions:
And apply the correct labels and milestones. Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon! Remember to remove the If these instructions are inaccurate, feel free to suggest an improvement. |
(cherry picked from commit 2c68dd3)
doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.lets see if the new release addresses the failures