You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Xavier Dury (Jira)" <ji...@apache.org> on 2021/03/26 14:53:00 UTC
[jira] [Comment Edited] (SUREFIRE-1659) Log4j logger in
TestExecutionListener corrupts Surefire's STDOUT.
[ https://issues.apache.org/jira/browse/SUREFIRE-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17309448#comment-17309448 ]
Xavier Dury edited comment on SUREFIRE-1659 at 3/26/21, 2:52 PM:
-----------------------------------------------------------------
I have the same problem with slf4j/logback:
{code:xml}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>3.0.0-M5</version>
<configuration>
<systemPropertyVariables>
<java.util.logging.config.file>${project.basedir}/src/test/resources/logging.properties</java.util.logging.config.file>
</systemPropertyVariables>
</configuration>
</plugin>
{code}
with {{src/test/resources/logging.properties}} containing:
{code}
handlers = org.slf4j.bridge.SLF4JBridgeHandler
{code}
I tried to fix this in https://github.com/apache/maven-surefire/pull/342, if other people could build/test/check to validate this fix works for them...
was (Author: kalgon):
I have the same problem with slf4j/logback:
{code:xml}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>3.0.0-M5</version>
<configuration>
<systemPropertyVariables>
<java.util.logging.config.file>${project.basedir}/src/test/resources/logging.properties</java.util.logging.config.file>
</systemPropertyVariables>
</configuration>
</plugin>
{code}
with {{src/test/resources/logging.properties}} containing:
{code}
handlers = org.slf4j.bridge.SLF4JBridgeHandler
{code}
> Log4j logger in TestExecutionListener corrupts Surefire's STDOUT.
> -----------------------------------------------------------------
>
> Key: SUREFIRE-1659
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1659
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 3.0.0-M3
> Reporter: Stig Rohde Døssing
> Priority: Major
> Attachments: src.zip, surefire-stdout-corrupt.zip
>
>
> I have a project that registers a JUnit 5 TestExecutionListener. The TestExecutionListener contains an SLF4j Logger, using Log4j2 as the underlying library. There is a log4j2.xml on the classpath, logging to console, and Surefire is set up to redirect output.
> Running the tests gives the following result.
> {quote}
> [WARNING] Corrupted STDOUT by directly writing to native stream in forked JVM 1. See FAQ web page and the dump file ...
> {quote}
> I've attached a minimal reproduction.
> Doing either of the following eliminates the error:
> * Not having the log4j2.xml on the classpath
> * Not having the Logger in the TestExecutionListener
--
This message was sent by Atlassian Jira
(v8.3.4#803005)