-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Some tests require non-zero tolerance #5647
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
I am seeing the following failures with tiny difference when running locally on my mac with the local freetype. Some of them are above so it may just tweaking the values
|
I added a PR #5734 that adjusts the tolerance slight so that the spectrogram tests passes for me |
In addition it seems like One example this happens even in the python 3.5 job which does not use multiprocessing so it's probably not related to that
|
Sorry I restarted the job so the log is gone |
I've also seen the I think the other tests might have a different root cause -- elsewhere I've seen this because a dictionary is being iterated over resulting in unpredictable ordering of drawing. Haven't looked into this deeply enough to determine if that's what's going on here, though. |
See also #5922 for additional test failures on windows for which the tolerance had to be changed. |
Added the test failures on appveyor/windows from #5922 directly to the todo list in the first comment |
Is this just Python 2/3 and versions of Numpy? If so, there would probably be only a few possible correct results for each test case. We could modify the comparison tests to allow several alternatives for the correct result, and compare against each of those with zero tolerance. It would be somewhat more work to update test cases for any other changes, but we could probably just pick the images from failing Travis tests. |
#7573 should have helped deal with 2 vs. 3 issues. IMO from matplotlib's perspective in general, we're doing something wrong if test results depend on 2 vs. 3 independent of versions of other things. |
This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help! |
I am going to close this as
|
Some are producing ever-so-slightly nondeterministic results, and others demonstrate a Python 2 vs. 3 issue. While #5307 got most of these stuff, these were punted on because obvious solutions haven't yet been found.
appveyor/windows: as part of #5922 added or increased tolerance for failures on:
-> currently set to 0.03, set tolerance to 0.05 on windows
This has a black diff, so up the tolerance on windows to 0.013
This looks actually interesting: it seems that only the middle figure in the last row is different
Also looks black, but only on py27/x86...?
The text was updated successfully, but these errors were encountered: