Test failure with Python 3.2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
subunit |
Fix Released
|
High
|
Robert Collins |
Bug Description
subunit-0.0.14 introduced 1 test failure with Python 3.2. This failure does not occur with Python 3.3.
$ PYTHONPATH="python" python3.2 -m testtools.run subunit.test_suite
Tests running...
=======
FAIL: subunit.
-------
Traceback (most recent call last):
File "/tmp/python-
file_
File "/tmp/python-
self.
File "/usr/lib64/
self.
File "/usr/lib64/
raise MismatchError(
testtools.
reference = [('status',
'subunit.parser',
None,
None,
True,
'Packet data',
b'\xb3-
True,
None,
None,
None),
('status',
'subunit.parser',
'fail',
None,
True,
'Parser Error',
b'UTF8 string at offset 2 contains NUL byte',
True,
None,
None,
None)]
actual = [('status',
'b\x00r',
'success',
None,
True,
None,
None,
False,
None,
'source',
None)]
Ran 307 tests in 1.504s
FAILED (failures=1)
Changed in subunit: | |
milestone: | none → next |
status: | Triaged → Fix Committed |
assignee: | nobody → Robert Collins (lifeless) |
Changed in subunit: | |
status: | Fix Committed → Fix Released |
Thanks for reporting this - I can't reproduce in 0.0.15. this -might- be a duplicate bug 1216163