subunit-filter mangles time information
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
subunit |
Fix Released
|
Critical
|
Jonathan Lange |
Bug Description
Consider the following subunit stream:
time: 2000-01-01 00:00:00.000000Z
test: foo
time: 2000-01-02 00:00:00.000000Z
success: foo
time: 2000-01-03 00:00:00.000000Z
According to the subunit README, this stream implies that test "foo" started on 2000-01-01 and completed successfully exactly 24hrs later.
If you run this through subunit-filter, you get this stream as output:
time: 2000-01-01 00:00:00.000000Z
time: 2000-01-02 00:00:00.000000Z
test: foo
successful: foo
time: 2000-01-03 00:00:00.000000Z
Which, according to the README means that the test "foo" started and finished at midnight of 2000-01-02, taking no time at all.
subunit-filter should not change the meaning of the time statements in the stream. In this example, the output should be exactly the same as the input (perhaps without the final 2000-01-03 time, but that's the subject of a different discussion, see https:/
Related branches
- Subunit Developers: Pending requested
- Diff: 0 lines
Changed in subunit: | |
status: | New → Triaged |
importance: | Undecided → Critical |
Changed in subunit: | |
assignee: | nobody → Jonathan Lange (jml) |
status: | Triaged → In Progress |
Changed in subunit: | |
status: | In Progress → Fix Committed |
milestone: | none → next |
Changed in subunit: | |
status: | Fix Committed → Fix Released |