subunit-ls time handling if time not first instruction broken

Bug #785954 reported by Robert Collins
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
subunit
Fix Released
Critical
Robert Collins

Bug Description

test: canonical.testing.layers.FunctionalLayer:tearDown
time: 2011-05-20 16:37:05.820858Z

will cause

Traceback (most recent call last):
  File "/usr/bin/subunit-ls", line 39, in <module>
    test.run(result)
  File "/home/robertc/source/unittest/subunit/working/python/subunit/__init__.py", line 1151, in run
    protocol.lostConnection()
  File "/home/robertc/source/unittest/subunit/working/python/subunit/__init__.py", line 558, in lostConnection
    self._state.lostConnection()
  File "/home/robertc/source/unittest/subunit/working/python/subunit/__init__.py", line 354, in lostConnection
    self.parser._lostConnectionInTest(_u(''))
  File "/home/robertc/source/unittest/subunit/working/python/subunit/__init__.py", line 554, in _lostConnectionInTest
    self.client.stopTest(self._current_test)
  File "/usr/lib/python2.7/dist-packages/testtools/testresult/real.py", line 555, in stopTest
    return self.decorated.stopTest(test)
  File "/home/robertc/source/unittest/subunit/working/python/subunit/test_results.py", line 471, in stopTest
    test_duration = self._time() - self._start_time
TypeError: unsupported operand type(s) for -: 'datetime.datetime' and 'int'

Changed in subunit:
status: New → Triaged
importance: Undecided → Critical
summary: - time handling if time not first instruction broken
+ subunit-ls time handling if time not first instruction broken
Changed in subunit:
assignee: nobody → Robert Collins (lifeless)
milestone: none → next
Changed in subunit:
status: Triaged → Fix Committed
Changed in subunit:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.