Running testr with --subunit option always returns 0

[Roman Podoliaka]

Consider the following test suite:

import unittest

class Test(unittest.TestCase):
    def test_case1(self):
        self.assertTrue(3 > 1) # success

    def test_case2(self):
        self.assertTrue(5 > 1) # success

    def test_case3(self):
        self.assertTrue(2 < 1) # fail

    def test_case4(self):
        self.assertTrue(1 > 2) # fail

    def test_case5(self):
        self.assertTrue(0 > 2) # fail

.testr.conf:

[DEFAULT]
test_command=python -m subunit.run discover . $LISTOPT $IDOPTION
test_id_option=--load-list $IDFILE
test_list_option=--list

Running tests with "testr run" works great:
rpodolyaka@rpodolyaka-pc:~/sandbox/tesrt$ testr run > /dev/null
(venv)rpodolyaka@rpodolyaka-pc:~/sandbox/tesrt$ echo $?
1

The process exit code is 1, because the test suite failed, and this was expected.

However, when --subunit option is used, the exit code is always 0, even if some tests fail:
(venv)rpodolyaka@rpodolyaka-pc:~/sandbox/tesrt$ testr run --subunit > /dev/null
(venv)rpodolyaka@rpodolyaka-pc:~/sandbox/tesrt$ echo $?
0

[Robert Collins (lifeless)]

This is deliberate, because it's up to the subunit consumer to decide success/fail, as long as the stream was successfully generated.

[Robert Collins (lifeless)]

Can you describe what problem this causes for you?

[Robert Collins (lifeless)]

Timing the bug out after nearly a year with no reply.