maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file
Date Thu, 04 May 2017 21:38:04 GMT

    [ https://issues.apache.org/jira/browse/SUREFIRE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997475#comment-15997475
] 

Tibor Digana commented on SUREFIRE-1359:
----------------------------------------

I will write a documentation and FAQ.

> 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)

Mime
View raw message