[SUREFIRE-1659] Log4j logger in TestExecutionListener corrupts Surefire's STDOUT.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-M3
• Fix Version/s: 2.22.3, 3.0.0-M6
• Assignee: Tibor Digana
• Reporter: Stig Rohde Døssing
• Created: 09/Apr/19 20:26
• Updated: 06/Apr/22 12:55
• Resolved: 31/Mar/21 09:44

Description

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.

[WARNING] Corrupted STDOUT by directly writing to native stream in forked JVM 1. See FAQ web page and the dump file ...

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

Issue Links

• is related to: SUREFIRE-1614 JUnit Runner that writes to System.out corrupts Surefire's STDOUT when using JUnit's Vintage Engine
• relates to: SUREFIRE-2058 Corrupted STDOUT by directly writing to native stream in forked JVM 1 with UTF-8 console logging
• links to: GitHub Pull Request #342