Lots of failing tests raising KnownFailureTest

Hi

When running the testsuite for matplotlib-1.2.0 i.e.

$ nosetests -exe matplotlib

I'm getting a lot of errors of the form:

···

======================================================================

ERROR: matplotlib.tests.test_dates.test_empty_date_with_year_formatter.test
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/case.py",
line 197, in runTest
    self.test(*self.arg)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/matplotlib/testing/decorators.py",
line 72, in test
    self._func()
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/matplotlib/testing/decorators.py",
line 47, in failer
    raise KnownFailureTest(msg) # An error here when running nose
means that you don't have the
matplotlib.testing.noseclasses:KnownFailure plugin in use.
KnownFailureTest: Test known to fail

----------------------------------------------------------------------

I would expect that these known tests should fail quietly. Shouldn't they?

Cheers

Adam

PS: I'm using python-2.7.3, nose-1.2.1 on Mac OS X 10.8.2 compiled
from MacPorts.

Does the same thing happen with the following command:

python -c “import matplotlib; matplotlib.test()”

I haven’t used nosetest before, so I have no clue if it does anything different than we expect.

Ben Root

···

On Sun, Nov 18, 2012 at 5:51 PM, Adam Mercer <ramercer@…287…> wrote:

Hi

When running the testsuite for matplotlib-1.2.0 i.e.

$ nosetests -exe matplotlib

I’m getting a lot of errors of the form:

Hello,

···

Hi

When running the testsuite for matplotlib-1.2.0 i.e.

$ nosetests -exe matplotlib

This is not the “correct” way to run the tests. You need to run them using:

python tests.py

I currently have a PR that indicates that in the README

I’m getting a lot of errors of the form:

Does the same thing happen with the following command:

python -c “import matplotlib; matplotlib.test()”

That’s another way of running the tests on matplotlib.

I haven’t used nosetest before, so I have no clue if it does anything different than we expect.

“KnownFailure” is not a “default” nosetest packages. Hence, we have to load it manually when running the tests.

Hence, all the tests that are known to fail actually fail, so that what we “expect”.

Cheers,

N

Ben Root


Monitor your physical, virtual and cloud infrastructure from a single

web console. Get in-depth insight into apps, servers, databases, vmware,

SAP, cloud infrastructure, etc. Download 30-day Free Trial.

Pricing starts from $795 for 25 servers or applications!

http://p.sf.net/sfu/zoho_dev2dev_nov


Matplotlib-users mailing list

Matplotlib-users@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/matplotlib-users

This is not the "correct" way to run the tests.

Then that explains it, thanks.

Does the same thing happen with the following command:

python -c "import matplotlib; matplotlib.test()"

No, all tests pass (or fail when they are expected to).

"KnownFailure" is not a "default" nosetest packages. Hence, we have to load
it manually when running the tests.

Thanks, makes sense.

Cheers

Adam

···

On Mon, Nov 19, 2012 at 7:44 AM, Nelle Varoquaux <nelle.varoquaux@...287...> wrote: