[
https://issues.apache.org/jira/browse/SUREFIRE-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164489#comment-17164489
]
Tibor Digana edited comment on SUREFIRE-1788 at 7/24/20, 3:18 PM:
------------------------------------------------------------------
[~kriegaex]
Mixed characters and strings look like the application locking problem.
But it mostly looks like the low level logger is not locking the print-line in
the Maven.
If you see how the implementation of the OutputStream looks like, you see the
synchronized methods on write(int) and write(byte[]) as well. But if a custom
OS does not synchronize the write(byte[]) then the effect would be as you have
depicted.
Let me please analyse this today.
You may help me if you like.
was (Author: tibor17):
[~kriegaex]
Mixed characters and strings look like the application locking problem.
But it mostly looks like the low level logger not locking while line in the
Maven.
If you see how the implementation of the OutputStream looks like, you see the
synchronized methods on write(int) and write(byte[]) as well. But if a custom
OS does not synchronize the write(byte[]) then the effect would be as you have
depicted.
Let me please analyse this today.
You may help me if you like.
> 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)
