On Fri, Aug 20, 2010 at 04:24:30PM -0700, Dan Stromberg's pytest wrote: > Ran 388 test cases in 11.22s (0.20s CPU), 15 errors, 5 failures, 21 skipped > 17 modules OK (6 failed) > failures: > /home/dstromberg/src/pylint-3k/common/build/lib/logilab/common/test/unittest_configuration > [1/13], > /home/dstromberg/src/pylint-3k/common/build/lib/logilab/common/test/unittest_changelog > [1/1], > /home/dstromberg/src/pylint-3k/common/build/lib/logilab/common/test/unittest_testlib > [4/101], > /home/dstromberg/src/pylint-3k/common/build/lib/logilab/common/test/unittest_umessage > [4/4], > /home/dstromberg/src/pylint-3k/common/build/lib/logilab/common/test/unittest_shellutils > [3/21], > /home/dstromberg/src/pylint-3k/common/build/lib/logilab/common/test/unittest_fileutils > [7/12]
The issue are that pytest discovery finds test in the "build" directory generated by an unrelated `python setup.py build` step. You should not worry about those error, removing the temporary 'build' directory should remove this error. However, the fact that a lot of files are missing from installed 'test/data' directory are suspicious (one would like to have test either fully installed or not installed at all). -- Pierre-Yves David LOGILAB, Paris (France)
signature.asc
Description: Digital signature
_______________________________________________ Python-Projects mailing list Python-Projects@lists.logilab.org http://lists.logilab.org/mailman/listinfo/python-projects
