[
https://issues.apache.org/jira/browse/SUREFIRE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16674259#comment-16674259
]
Dan Tran commented on SUREFIRE-1359:
------------------------------------
[~MattNelson] I am experiencing the same issue. maven 3.6 java 1.8.0-171. How
did you implement the workaround?
> 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
> Priority: Major
> Attachments: 2017-04-13T10-56-35_635-jvmRun1.dumpstream,
> 2017-04-13T10-56-36_592.dumpstream, TEST-hm.binkley.labs.GitInfoIT.xml,
> TEST-hm.binkley.labs.GreetingControllerIT.xml, failsafe-summary.xml,
> hm.binkley.labs.GitInfoIT.txt, hm.binkley.labs.GreetingControllerIT.txt
>
>
> 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
(v7.6.3#76005)
