testtools-0.9.14 outplays subunit
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| testtools |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
Testing subunit-0.0.7, it fails to start the test suite. The testtools version 0.9.14 has made some change that renders it incomaptible.
archtester subunit # ebuild subunit-
libtool: link: x86_64-
make[1]: Nothing to be done for `runtests.py'.
make[1]: Leaving directory `/mnt/gen2/
make check-TESTS check-local
make[1]: Entering directory `/mnt/gen2/
Traceback (most recent call last):
File "./runtests.py", line 23, in <module>
from subunit.
File "/mnt/gen2/
from subunit.tests import (
File "/mnt/gen2/
from testtools.
ImportError: cannot import name Python26TestResult
FAIL: runtests.py
Running suite(s): subunit_child
100%: Checks: 6, Failures: 0, Errors: 0
PASS: c/tests/test_child
=======
1 of 2 tests failed
Please report to <email address hidden>
=======
make[1]: *** [check-TESTS] Error 1
make[1]: Leaving directory `/mnt/gen2/
make: *** [check-am] Error 2
* ERROR: dev-python/
* Testing failed with CPython 2.7 in python_
*
I'm still perplexed by the function name Python26TestResult. Initially it seemed it was seeking a non-existing function. The test suite works fine with testtools-0.9.11. The line is the same in subunit-
Ugh. Sorry. I don't know how this happened. We really need some integration bots that run released subunit against testtools. Static analysis reveals that the problem was introduced in testtools 0.9.12.
In any case, subunit trunk has this problem fixed. We're unlikely to do a point release for testtools 0.9.12, and I'd rather not restore the compatibility kludge. Would it be OK if we pushed for a new release of subunit instead?