[
https://issues.apache.org/jira/browse/SUREFIRE-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164076#comment-17164076
]
Alexander Kriegisch edited comment on SUREFIRE-1788 at 7/24/20, 1:52 AM:
-------------------------------------------------------------------------
That is one of the problems of interrupting a discussion for 3 weeks. Now I am
trying hard to remember what this was about exactly. Okay:
* The last problem we were talking about was about output lines getting mixed
up in M5.
* First I thought it only happens with active {{<forkNode implementation=...}}
option, but then I commented it out and am still seeing the lines mixed up. So
it is a general new problem in M5 which did not occur in M4.
* You were talking about "native calls penetration", but I actually don't know
what you mean by that technical term. Maybe that's where our misunderstanding
began.
* I also mentioned having noticed that by {{<disable>true</disable>}} I can
silence Surefire output in case I only want to see what my tests themselves
print to the console. This is just nice to know, not what I want. Tests should
not log but assert, but some of my tests log things anyway and often it helps
me find out more quickly what is going on. This is unrelated to the mix-up
problem, just a take-away from the code snippet you gave me.
What I want is very easy to explain (I am not saying easy to implement):
console log from both Surefire and my Java agent or them test themselves on
stdOut/Err to be visible on the console, but please without lines being mixed
up and without freezing my build due to module path problems.
was (Author: kriegaex):
That is one of the problems of interrupting a discussion for 3 weeks. Now I am
trying hard to remember what this was about exactly. Okay:
* The last problem we were talking about was about output lines getting mixed
up im M5.
* First I thought it only happens with active {{<forkNode implementation=...}}
option, but then I commented it out and am still seeing the lines mixed up. So
it is a general new problem in M5 which did not occur in M4.
* You were talking about "native calls penetration", but I actually don't know
what you mean by that technical term. Maybe that's where our misunderstanding
began.
* I also mentioned having noticed that by {{<disable>true</disable>}} I can
silence Surefire output in case I only want to see what my tests themselves
print to the console. This is just nice to know, not what I want. Tests should
not log but assert, but some of my tests log things anyway and often it helps
me find out more quickly what is going on. This is unrelated to the mix-up
problem, just a take-away from the code snippet you gave me.
What I want is very easy to explain (I am not saying easy to implement):
console log from both Surefire and my Java agent or them test themselves on
stdOut/Err to be visible on the console, but please without lines being mixed
up and without freezing my build due to module path problems.
> Unhandled native logs in SurefireForkChannel
> --------------------------------------------
>
> Key: SUREFIRE-1788
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1788
> Project: Maven Surefire
> Issue Type: Task
> Components: Maven Failsafe Plugin, Maven Surefire Plugin, process
> forking
> Reporter: Tibor Digana
> Assignee: Tibor Digana
> Priority: Major
> Fix For: 3.0.0-M5
>
>
> This is related only to the internal change of the version 3.0.0-M5 itself.
> The
> [stdOut|https://github.com/apache/maven-surefire/blob/master/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/extensions/SurefireForkChannel.java#L153]
> should be printed to INFO on the console.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
