XN137 opened a new issue, #3412: URL: https://github.com/apache/maven-surefire/issues/3412
### Affected version 3.5.5+ ### Bug description see [comment](https://github.com/apache/maven-surefire/pull/3338#issuecomment-4190810411) the integration test added in https://github.com/apache/maven-surefire/pull/3338 documents the current (faulty?) behavior. reverting https://github.com/apache/maven-surefire/commit/b4a53de9b3a9ce02f306f02b064f4f58070678f4 brings back the old behavior of reporting class teardown issues as errors. why this matters: - a lot of test infrastructure can do important things on class teardown i.e. check for resource leaks, clean up for the next test etc. - even if intentional such a behavior change should not be introduced in a patch version imo also note that when `rerunFailingTestsCount > 0` passing tests are getting rerun on class teardown errors. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
