[
https://issues.apache.org/jira/browse/SUREFIRE-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17797986#comment-17797986
]
ASF GitHub Bot commented on SUREFIRE-1934:
------------------------------------------
kriegaex commented on PR #670:
URL: https://github.com/apache/maven-surefire/pull/670#issuecomment-1859378299
OK, I quickly looked at the code. This PR does nothing of the sort I was
talking about above. It does not change stdOut/stdErr capturing in any way,
just adds a switch adding the output to the XML report. I.e., which ever way
Surefire handles those streams in a multi-threading situation, remains the
same. Sorry for the misunderstanding and for the noise. I had hoped that
someone came up with a magical solution for the root problem. But it is not
being addressed here.
> Ability to disable system-out/system-err for successfuly passed tests
> ---------------------------------------------------------------------
>
> Key: SUREFIRE-1934
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1934
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
> Affects Versions: 3.0.0-M5
> Reporter: Andrey Turbanov
> Priority: Major
>
> After SUREFIRE-1744 surefire-plugin always reports system-out/system-err even
> for successfully passed test. A lot of old projects with big amount of tests
> now have to deal with huge output.
> I think there should be option to disable new behavior.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
