You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (Jira)" <ji...@apache.org> on 2020/05/04 15:28:00 UTC
[jira] [Commented] (SUREFIRE-1788) Unhandled native logs in
SurefireForkChannel
[ https://issues.apache.org/jira/browse/SUREFIRE-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17099038#comment-17099038 ]
Tibor Digana commented on SUREFIRE-1788:
----------------------------------------
Hi [~kriegaex],
The fix appears on [GitHub|https://github.com/apache/maven-surefire/pull/291]. Feel free to install the branch of Surefire and run your test with the agent in your project. This should work for you.
> 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)