kriegaex edited a comment on pull request #354: URL: https://github.com/apache/maven-surefire/pull/354#issuecomment-871822301
Sorry, @Tibor17, back in April I made a local commit to activate `SurefireForkNodeFactory` which before was commented out by default. I never pushed it. Please pull and try again. I thought you would have looked into the POM before you test. The rationale of deactivating it at first was to avoid the build from hanging and only opt in. For for a regression test, of course it is better to start from a state of activation. I also pushed another commit to master, containing some commented-out options for easily being able to switch between modes. If you extract ITs for Surefire, please be sure to use the latest versions of both branches. But BTW, at least with the commit you tested you see the output garbling (mixed output of stdErr and stdLog) in non-`SurefireForkNodeFactory` mode, which I mentioned long ago in the Jira issue, because write access to the console it is not synchronised on at least a per-line level. So your test with commit had the nice side effect of reminding you of this open issue, too. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
