Hello, Sounds like the default console logger for the JUL root gets the events and writes them to stdout.
Did you try to use an anonymous logger or specify setUseParentHandler(false) on your trace logger? Doesn’t sound very surefire or maven specific, that would also happen in a stand alone execution. Gruss Bernd -- http://bernd.eckenfels.net ________________________________ Von: Laurian Angelescu <[email protected]> Gesendet: Friday, March 11, 2022 3:56:16 PM An: [email protected] <[email protected]> Betreff: Want to understand the .dumpstream file contents I've built a trivial Java agent that uses java.util.logging.Logger and a FileHandler to trace out the program into a log file. I've attached a log file produced as a sample: agent_03112022_064424.log. The point is to run some tests under instrumentation. To do so I run: mvn test -DargLine="-javaagent:C:\JARS\agent.jar" on a target project, also built with Maven, to run a test suite under instrumentation. After completion, the folder /target/surefire-reports contains file 2022-03-11T07-01-03_983.dumpstream which contains similar information to the agent_03 log file. I want to understand why the surefire dumpstream contains the traces I am outputting using the logger in my agent code (to the agent_03 file)? The agent is a self-contained JAR and is outputting to its own file. The surefire plugin is running tests on a completely different package. The second question is how do I turn it off?
