[
https://issues.apache.org/jira/browse/SUREFIRE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970102#comment-15970102
]
Tibor Digana commented on SUREFIRE-1359:
----------------------------------------
[~binkley]
>> it complains about "corrupted stdin stream", but the exit code is 0.
Does it mean that you did not see full log due to {{.mvn/jvm.config}}?
> 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
> 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)
