You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Bipin Prasad (Jira)" <ji...@apache.org> on 2021/02/04 07:34:00 UTC
[jira] [Commented] (STORM-3741) Maven Surefire plugin corrupts
output and creates an excessive log file
[ https://issues.apache.org/jira/browse/STORM-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17278618#comment-17278618 ]
Bipin Prasad commented on STORM-3741:
-------------------------------------
Pull Request: https://github.com/apache/storm/pull/3375
> Maven Surefire plugin corrupts output and creates an excessive log file
> -----------------------------------------------------------------------
>
> Key: STORM-3741
> URL: https://issues.apache.org/jira/browse/STORM-3741
> Project: Apache Storm
> Issue Type: Bug
> Reporter: Bipin Prasad
> Assignee: Bipin Prasad
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When running tests (mvn test) with "reuseForks=true", the STDOUT gets corrupted.
> You will see a message like this:
> {code}
> [WARNING] Corrupted STDOUT by directly writing to native stream in forked JVM 1. See FAQ web page and the dump file […]
> {code}
> This problem goes away when "reuseForks=false". This problem has been fixed in surefire versions 2.22.2 and 3.0.0-M3 as documented here: https://issues.apache.org/jira/browse/SUREFIRE-1614
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)