Skip to content
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

Travis error is MacOS image tolerance of 0.005 for test_constrained_layout.py::test_colorbar_location #12433

Closed
jklymak opened this issue Oct 7, 2018 · 6 comments · Fixed by #12683
Milestone

Comments

@jklymak
Copy link
Member

jklymak commented Oct 7, 2018

Originally posted by @jklymak in #12431

Travis error is MacOS image tolerance of 0.005 changing for test_constrained_layout.py::test_colorbar_location. Not sure what changed on macOS to cause this, but it doesn't affect this PR.

@tacaswell tacaswell added this to the v3.0.x milestone Oct 7, 2018
@jklymak
Copy link
Member Author

jklymak commented Oct 15, 2018

This seems to have fixed itself 🤷‍♂️

@jklymak jklymak closed this as completed Oct 15, 2018
@QuLogic
Copy link
Member

QuLogic commented Oct 31, 2018

I assume you don't know what the result looks like; I just hit this trying to build a package locally, so here's what it looks like:
test_colorbar_location
Note that in this case, the RMS is much higher: 78.990.

@QuLogic QuLogic reopened this Oct 31, 2018
@QuLogic QuLogic modified the milestones: v3.0.1, v3.0.x Oct 31, 2018
@jklymak
Copy link
Member Author

jklymak commented Oct 31, 2018

Yeah, its just a flaky test. 90% of the time, if you rerun it, it'll look correct...

I'm guessing the constraint solver gets in a bad loop sometimes or finds an incorrect minima?

Does it really take a long time if this happens for you?

@jklymak
Copy link
Member Author

jklymak commented Oct 31, 2018

Also open to suggestions - happy to simplify the test - its a bit of a crazy figure 😉

@jklymak
Copy link
Member Author

jklymak commented Oct 31, 2018

i.e. #12678 it failed, and I reran the CI it failed on and it passed...

@QuLogic
Copy link
Member

QuLogic commented Oct 31, 2018

I mean, it was the full test suite, so whether it was slower wasn't particularly noticeable. I also re-ran just the one test 100 times over and it never failed, so...

Should we just mark it as flaky then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants