Given that JUnit4 for EOLed several years ago, I wonder if we really want to do this. The current state of the art is to run JUnit4 tests with the JUnit5 Vintage engine, and test_status and test_failure are reported correctly in that configuration.
Having said that, it appears that one or more of the current JUnit4 hook are broken, which is causing this. At the very, least, we shouldn't crash the process when running JUnit4 tests.
Given that JUnit4 for EOLed several years ago, I wonder if we really want to do this. The current state of the art is to run JUnit4 tests with the JUnit5 Vintage engine, and test_status and test_failure are reported correctly in that configuration.
Having said that, it appears that one or more of the current JUnit4 hook are broken, which is causing this. At the very, least, we shouldn't crash the process when running JUnit4 tests.