Merge lp:~jml/subunit/use-traceback-content into lp:~subunit/subunit/trunk
Proposed by
Jonathan Lange
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 161 | ||||
Proposed branch: | lp:~jml/subunit/use-traceback-content | ||||
Merge into: | lp:~subunit/subunit/trunk | ||||
Diff against target: |
90 lines (+16/-14) 2 files modified
python/subunit/__init__.py (+4/-4) python/subunit/tests/test_test_protocol.py (+12/-10) |
||||
To merge this branch: | bzr merge lp:~jml/subunit/use-traceback-content | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jelmer Vernooij | Approve | ||
Review via email: mp+92337@code.launchpad.net |
Description of the change
This addresses bug 929063 by making subunit call TracebackContent rather than _exc_info_
The tests fail for me, but they fail with trunk too. I suspect subunit is out of step with recent testtools formatting changes. This branch doesn't introduce any new failures that I can tell.
Perhaps it's best to land this branch after the testtools side of the fix, https:/
To post a comment you must log in.
The most recent changes (r159) make subunit's Python tests pass with testtools 0.9.11 (the documented minimum version) and with testtools trunk. Actually, it doesn't quite make them work with 0.9.11 because the TracebackContent fix in __init__.py requires 0.9.12 minimum to work.
Let me know if you want me to make that work in 0.9.11 and with trunk. Personally I think we could just make the next release of subunit say minimum testtools 0.9.13 (not yet released) and ditch the compatibility workarounds.
4 shell tests still fail due to test_function_ output. sh not expecting time output.