Hello,
while testing 2.0.0b4 on debian unstable, there are a lot of ImageComparisonFailure. it seems that the same test is executed twice, and the first execution always fails, for example:
matplotlib.tests.test_axes.test_canonical.test ... FAIL
matplotlib.tests.test_axes.test_canonical.test ... ok
matplotlib.tests.test_axes.test_canonical.test ... ok
... ... ...
FAIL: matplotlib.tests.test_axes.test_canonical.test
----------------------------------------------------------------------
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
File "/build/matplotlib-2.0.0~beta4/build/lib.linux-x86_64-2.7/matplotlib/testing/decorators.py", line 58, in failer
result = f(*args, **kwargs)
File "/build/matplotlib-2.0.0~beta4/build/lib.linux-x86_64-2.7/matplotlib/testing/decorators.py", line 261, in do_test
'(RMS %(rms).3f)'%err)
ImageComparisonFailure: images not close: /build/matplotlib-2.0.0~beta4/result_images/test_axes/canonical.png vs. /build/matplotlib-2.0.0~beta4/result_images/test_axes/canonical-expected.png (RMS 0.003)
(that is the 2.7 failure, but it happens also on 3.5 and on their debug flavor interpreters).
the grand total of the testsuite is FAILED (KNOWNFAIL=69, SKIP=14, failures=887)
please let me know how i can help you debug this
Hello,
while testing 2.0.0b4 on debian unstable, there are a lot of ImageComparisonFailure. it seems that the same test is executed twice, and the first execution always fails, for example:
(that is the 2.7 failure, but it happens also on 3.5 and on their debug flavor interpreters).
the grand total of the testsuite is
FAILED (KNOWNFAIL=69, SKIP=14, failures=887)please let me know how i can help you debug this