You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mnemonic.apache.org by "Gordon King (Jira)" <ji...@apache.org> on 2021/07/06 06:24:00 UTC

[jira] [Created] (MNEMONIC-659) Corrupted STDOUT by directly writing to native stream in forked JVM

Gordon King created MNEMONIC-659:
------------------------------------

             Summary: Corrupted STDOUT by directly writing to native stream in forked JVM
                 Key: MNEMONIC-659
                 URL: https://issues.apache.org/jira/browse/MNEMONIC-659
             Project: Mnemonic
          Issue Type: Task
          Components: TestCase
    Affects Versions: 0.16.0
            Reporter: Gordon King
            Assignee: Gordon King
             Fix For: 0.16.0


After the maven-surefire-plugin got upgraded to 3.0.0-M3, the maven testing reports the following message on mnemonic-core.
{code:java}
Corrupted STDOUT by directly writing to native stream in forked JVM 1. See FAQ web page and the dump file /home/gary/mnemonic/mnemonic-core/target/surefire-reports/2021-07-05T22-42-57_481-jvmRun1.dumpstream{code}
Found the official explanation in [https://maven.apache.org/surefire/maven-surefire-plugin/faq.html#corruptedstream]

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)