[
https://issues.apache.org/jira/browse/SUREFIRE-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480775#comment-17480775
]
Tibor Digana commented on SUREFIRE-1983:
----------------------------------------
version 2.22.3,
https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=8ca99dd046382784d8231741245cc24afcf06ead
> Corrupted STDOUT by directly writing to native stream in forked JVM 1.
> [setupJunitLogger() should be called AFTER startCapture()]
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-1983
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1983
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support, Maven Failsafe Plugin, Maven Surefire
> Plugin
> Reporter: Tibor Digana
> Assignee: Tibor Digana
> Priority: Major
> Fix For: 2.22.3, 3.0.0-M6
>
>
> The warning messages "Corrupted STDOUT by directly writing to native stream
> in forked JVM 1." appear in Surefire JUnit5 provider. In order to reproduce
> this issue with old versions, Log4j or slf4j logger should be used. The
> previous fixes were not reliable. The real root cause of this issue is based
> on incorrect order of methods startCapture() and setupJunitLogger().
> setupJunitLogger() should be called AFTER startCapture()
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
