-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
CI: matplotlib failures #26714
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
Comments
Seems to be a change in matplotlib. The test passes for me locally, with 3.0.3, fails with 3.1.0. (cc @tacaswell, in case this wasn't deliberate. Sorry I don't have an MPL-only reproducer right now) Just going to change the assert for 3.1.0+ for now. |
@TomAugspurger i looked into this, xref #26582, the best i could come up with is that we are using an undocumented method in the test. maybe not part of the official api. our code suggests that we assume a patch object but are testing a text object. |
My first guess was https://matplotlib.org/api/api_changes.html?highlight=api#major-minor-tick-collisions where we now hide ticks that collide by default, but the issue is things are visible that should not be. Does the image actually look different? |
No it looks the same afaict.
… On Jun 7, 2019, at 18:45, Thomas A Caswell ***@***.***> wrote:
My first guess was https://matplotlib.org/api/api_changes.html?highlight=api#major-minor-tick-collisions where we now hide ticks that collide by default, but the issue is things are visible that should not be.
Does the image actually look different?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
https://travis-ci.org/pandas-dev/pandas/jobs/542921706#L2423
I'm looking into it now, but will have to go in 30 minutes.
The text was updated successfully, but these errors were encountered: