[ https://issues.apache.org/jira/browse/SUREFIRE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997312#comment-15997312 ]
Matt Nelson commented on SUREFIRE-1359: --------------------------------------- {quote} There is no property since it is not Surefire problem. The IT tool should now provide a fix. Can you attach your project in Jira and I will try to reproduce the issue. If the IT framework is Arquillian then this issue was already fixed there. {quote} This is a plugin problem since it worked with 2.19.1. The refactoring of the ForkedClient is now inspecting the output of all forked processes (even those which surefire did not spawn). When the output line of a process does not match the expected prefixes it blows up. Even when I modify the log format pattern of the my forked processes to include the stdout prefix {{3,}} any multiline messages still cause the failures. > Corrupted stdin stream in forked JVM 1. See the dump file > --------------------------------------------------------- > > Key: SUREFIRE-1359 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1359 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin > Affects Versions: 2.20 > Environment: JDK 1.8.0_121 > maven version 3.5.0 > Reporter: Brian Oxley > Assignee: Tibor Digana > Attachments: 2017-04-13T10-56-35_635-jvmRun1.dumpstream, > 2017-04-13T10-56-36_592.dumpstream, failsafe-summary.xml, > hm.binkley.labs.GitInfoIT.txt, hm.binkley.labs.GreetingControllerIT.txt, > TEST-hm.binkley.labs.GitInfoIT.xml, > TEST-hm.binkley.labs.GreetingControllerIT.xml > > > Surefire 2.20 complains "Corrupted stdin stream in forked JVM 1. See the dump > file". Version 2.19.1 does not, and testing completes successfully. > Project is here: https://github.com/binkley/sproingk. > Run with "mvn clean verify". > Same behavior on Windows 10 (Oracle JDK), MacOS and the Linux subsystem on > Windows. -- This message was sent by Atlassian JIRA (v6.3.15#6346)