If tests are killed, no failure is visible

[hakanai]

With the JUnit reporter, if the tests are killed externally (e.g. if they take too long to run), one of the XML files will have length 0 and Jenkins will fail to parse it. This then shows up as a test failure on Jenkins.

With CI::Reporter, if the tests are killed externally, they just exit and no XML file is written at all. This shows up as a successful build.

Granted, the return code is non-zero, but it seems like a hack for me to create a zero-length XML file on the event of a non-zero return code, just to trick Jenkins.

[shepmaster]

We are in the process of cleaning out old issues. If this issue still
applies to this version, please let us know, otherwise we're going to
close this issue to focus on current problems. Thanks for your report!

[hakanai]

This still does happen, even since we switched to RSpec. You can verify it by making a spec which just calls sleep(6000) and then kill -9 the process while the test is running.