Cannot rerun failing when the failure is an import one
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
testtools |
Triaged
|
Medium
|
Unassigned |
Bug Description
I'm using testr to run some tests where I'm moving things around. There are module import failures.
jml@truth:
running=
=======
ERROR: unittest.
-------
ImportError: Failed to import test module: tests.test_
Traceback (most recent call last):
File "/usr/lib/
module = self._get_
File "/usr/lib/
__import_
File "/home/
from pkgme.backend import ExternalHelpers
ImportError: No module named pkgme.backend
=======
ERROR: unittest.
-------
ImportError: Failed to import test module: tests.test_binary
Traceback (most recent call last):
File "/usr/lib/
module = self._get_
File "/usr/lib/
__import_
File "/home/
from devportalbinary
File "devportalbinar
from pkgme.info_elements import (
ImportError: No module named pkgme.info_elements
id=14, tests=2, failures=2
When I re-run the tests with 'run --failing', I get this:
jml@truth:
running=
Traceback (most recent call last):
File "/usr/lib/
"__main__", fname, loader, pkg_name)
File "/usr/lib/
exec code in run_globals
File "/usr/lib/
stdout=
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
self.test = loader.
File "/usr/lib/
raise ImportError('Start directory is not importable: %r' % start_dir)
ImportError: Start directory is not importable: 'unittest.
id=15, tests=0
Note that the test ids are incorrect: unittest.
Changed in subunit: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Testrepository doesn't know what an 'import failure' is; this is up to the runner to report test ids that can be fed back in to load-list or similar in a meaningful way.