nose-devs
test generation failures swallowed silently by such createTests
AttributeErrors during test generation are swallowed silently unless the test module is explicitly loaded. In that case, they are hard to debug because they appear only as test failures with no usable traceback.
I believe I just got bitten by this bug. Or at least it seems related. I had incorrectly defined pythonpath. When running in sequence (i.e. plain 'nose2') I get the stack traces showing the import errors. However when running in parallel ('nose2 --plugin=nose2.plugins.mp -N 20') all I see is:
test_not_found (nose2.loader.LoadTestsFailure) ... ERROR
test_not_found (nose2.loader.LoadTestsFailure) ... ERROR
test_not_found (nose2.loader.LoadTestsFailure) ... ERROR
test_not_found (nose2.loader.LoadTestsFailure) ... ERROR
======================================================================
ERROR: test_not_found (nose2.loader.LoadTestsFailure)
----------------------------------------------------------------------
AttributeError: 'module' object has no attribute 'ModuleImportFailure'
======================================================================
ERROR: test_not_found (nose2.loader.LoadTestsFailure)
----------------------------------------------------------------------
AttributeError: 'module' object has no attribute 'ModuleImportFailure'
....
Could any of you please provide a regression test or a code example so I can understand better what is wrong and how to fix it exactly?
Actually, you can ignore my comment. On further investigation the thing I'm referring to is a bug in the mp plugin
