Comment 1 for bug 1568922

Revision history for this message
Matthew Treinish (treinish) wrote :

This is actually an underlying issue with testr that has been so longstanding that ostestr tries to work around it. Testr reports 2 failures 1 of which is an internal artifact and subunit-trace (which is the output filter being used by ostestr) is filtering that from the test results:

https://github.com/openstack/os-testr/blob/master/os_testr/subunit_trace.py#L170-L172

However, the count generation just looks at the raw result output and counts test states (and since there are 2 failures in the output, without any other context) the count shows both.

https://github.com/openstack/os-testr/blob/master/os_testr/subunit_trace.py#L252-L259