[
https://issues.apache.org/jira/browse/SUREFIRE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997468#comment-15997468
]
Tibor Digana commented on SUREFIRE-1359:
----------------------------------------
[~MattNelson]
In the future, means version 3.0, we will use sockets where Maven and forked
process will communicate and avoid using std/out.
But without dumping these errors to {{target/surefire-reports/*.dump*}} and on
console we would permanently receive blocker issues and this would be very hard
to recognize who really corrupted the native stream. This stream is utilized by
Surefire to report result about your tests and send {{ReportEntry}} from forked
JVM to Maven process and then plugin in Maven process will create XML report,
fail the build if a test fails, etc.
> 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)
