[ https://issues.apache.org/jira/browse/SUREFIRE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995865#comment-15995865 ]
Matt Nelson commented on SUREFIRE-1359: --------------------------------------- This is still an issue in some workflows and I don't see a way to resolve it. I am using the ProcessBuilder to kick off process in our integration tests. I am also inheriting the IO of the std streams in order to get a unified console output from all the processes. Using the default pipe redirect does not work. https://docs.oracle.com/javase/8/docs/api/java/lang/ProcessBuilder.html#inheritIO-- Is there a recommendation for how to proceed with the corrupted streams? Can I set a property to disable this check? > 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)