-
Notifications
You must be signed in to change notification settings - Fork 416
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
Fix build #1352
Fix build #1352
Conversation
This apparently will be the default and the option is going away (in favor of opting-in to capture the output). Removing it silences a warning.
There's a ton of crap (warnings, out of date configs) that needs updating, but I'll get that later. I just want to see CI finally green, and we can pull this into the 0.12.x branch. |
One has minor pixel-level differences, the other looks like fallout from matplotlib fixing some text positioning and clipping issues.
This test was created before aspect ratio work, but merged after. We use aspect ratio='auto' to keep the images the same across matplotlib versions, but this test was missing it. It didn't matter until matplotlib 3.2 came out.
drop_vars is only available on xarray 0.14.0
Have to see what's going on later.
Update image to reflect matplotlib 3.2, and skip on all prior versions.
Not sure where this was used exactly, but this does not seem to be used anywhere now.
Just a small error in accessing the xarray site when CI was running. Should be good to go. Yay for maintenance work! Ugh. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No worries @jthielen. Something like that always creeps in while CI if failing for “known reasons”. |
Description Of Changes
Trying to get CI passing again. Mainly changes to fix tests with matplotlib 3.2 now that we have proper testing packages for it.
Checklist