kriegaex edited a comment on pull request #355: URL: https://github.com/apache/maven-surefire/pull/355#issuecomment-873712057
> Here is the [history ](https://github.com/kriegaex/maven-surefire/commits/before-SUREFIRE-1881)of commits in your repo - no fix! You don't get it, do you? This PR (branch `SUREFIRE-1881-fix` ) does contain the fixes! Branch `before-SUREFIRE-1881` is just for reproducing what would happen in case of a regression, because I needed a way to emulate that situation. What is so difficult to understand about it? This is why I named the other branch accordingly, with an explicit `before-` prefix in the branch name, and described it as a **backport**: > If you want to easily reproduce the hanging JVMs directly in Surefire ITs, **I ported both SUREFIRE-1881 tests from this PR back to the state before the merge.** Simply check out my branch [`before-SUREFIRE-1881`](https://github.com/kriegaex/maven-surefire/tree/before-SUREFIRE-1881), make a clean build without tests and then run the ITs. The easiest way is to temporarily add `<test>Surefire1881IT</test>` to the Failsafe config in the IT module. Of course you can also add the corresponding Maven CLI option. -- 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]
