[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file
[ 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)
[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file
[ https://issues.apache.org/jira/browse/SUREFIRE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997582#comment-15997582 ] Matt Nelson commented on SUREFIRE-1359: --- Thanks for all the support, I have implemented 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 > 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)
[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file
[ 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)
[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file
[
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)
[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file
[
https://issues.apache.org/jira/browse/SUREFIRE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997438#comment-15997438
]
Tibor Digana commented on SUREFIRE-1359:
[~MattNelson]
This problem was always, but nobody could see it in the logs. Here we only
notify you that something went wrong but not on surefire side. The entire
problem is that we have blocker and critical issues assigned against Maven
because the tests and frameworks print bytes to native std/out stream in the
forked jvm. Therefore we may decode it by mistake. This way we try to force the
f/w vendors to use {{System.out.print()}} instead of {{FileDescriptor.out}} and
{{ProcessBuilder.inheritIO()}}.
>>even those which surefire did not spawn
This sounds like the plugin process loaded test classes and static code which
has {{ProcessBuilder}}. We load the class first in plugin process and scan
{{@Test}} annotations and then in forked jvm second this and instantiating the
class via JUnit framework.
Please see SUREFIRE-1222. The Arquillian avoided using inherited channel:
https://github.com/tremes/arquillian-container-se/commit/8e8c4455af0412a363824690e77e8ee102fc3b9f
Maybe this helps.
> 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)
[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file
[
https://issues.apache.org/jira/browse/SUREFIRE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997312#comment-15997312
]
Matt Nelson commented on SUREFIRE-1359:
---
{quote}
There is no property since it is not Surefire problem. The IT tool should now
provide a fix. Can you attach your project in Jira and I will try to reproduce
the issue. If the IT framework is Arquillian then this issue was already fixed
there.
{quote}
This is a plugin problem since it worked with 2.19.1. The refactoring of the
ForkedClient is now inspecting the output of all forked processes (even those
which surefire did not spawn). When the output line of a process does not match
the expected prefixes it blows up. Even when I modify the log format pattern of
the my forked processes to include the stdout prefix {{3,}} any multiline
messages still cause the failures.
> 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)
[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file
[ https://issues.apache.org/jira/browse/SUREFIRE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996112#comment-15996112 ] Tibor Digana commented on SUREFIRE-1359: [~MattNelson] There is no property since it is not Surefire problem. The IT tool should now provide a fix. Can you attach your project in Jira and I will try to reproduce the issue. If it IT framework is Arquillian then this issue was already fixed there. > 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)
[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file
[ 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)
[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file
[ https://issues.apache.org/jira/browse/SUREFIRE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970103#comment-15970103 ] Brian Oxley commented on SUREFIRE-1359: --- That is correct. :) And I failed to check the exit status. > 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)
[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file
[
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)
[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file
[ https://issues.apache.org/jira/browse/SUREFIRE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970099#comment-15970099 ] Tibor Digana commented on SUREFIRE-1359: I used Windows 7 and java version "1.8.0_121". > 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)
[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file
[
https://issues.apache.org/jira/browse/SUREFIRE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970098#comment-15970098
]
Tibor Digana commented on SUREFIRE-1359:
[~binkley]
Now I changed surefire version to 2.20 in properties and this is the result:
{quote}
mvn test
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building Sproink 0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- git-commit-id-plugin:2.2.2:revision (default) @ sproingk ---
[INFO]
[INFO] --- jacoco-maven-plugin:0.7.9:prepare-agent (jacoco-initialize) @
sproingk ---
[INFO] argLine set to
-javaagent:D:\\.m2\\repository\\org\\jacoco\\org.jacoco.agent\\0.7.9\\org.jacoco.agent-0.7.9-runtime.jar=destfile=d:\\vcs\\github\\sproingk\\target\\jacoco.exec
[INFO]
[INFO] --- maven-dependency-plugin:3.0.0:sources (download-sources) @ sproingk
---
[INFO]
[INFO] --- maven-dependency-plugin:3.0.0:resolve (download-javadocs) @ sproingk
---
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ sproingk
---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] Copying 4 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.6.1:compile (default-compile) @ sproingk ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- kotlin-maven-plugin:1.1.1:compile (compile-kotlin) @ sproingk ---
[INFO] Kotlin Compiler version 1.1.1
[WARNING] Source root doesn't exist:
d:\vcs\github\sproingk\target\generated-sources\annotations
[INFO] Compiling Kotlin sources from [d:\vcs\github\sproingk\src\main\kotlin]
[INFO] Module name is sproingk
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
sproingk ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.6.1:testCompile (default-testCompile) @
sproingk ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- kotlin-maven-plugin:1.1.1:test-compile (test-compile-kotlin) @
sproingk ---
[INFO] Kotlin Compiler version 1.1.1
[WARNING] Source root doesn't exist:
d:\vcs\github\sproingk\target\generated-test-sources\test-annotations
[INFO] Compiling Kotlin sources from [d:\vcs\github\sproingk\src\test\kotlin]
[INFO] Module name is sproingk
[INFO]
[INFO] --- maven-surefire-plugin:2.20:test (default-test) @ sproingk ---
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 32.409 s
[INFO] Finished at: 2017-04-15T21:40:33+02:00
[INFO] Final Memory: 54M/482M
[INFO]
{quote}
> 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)
[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file
[ https://issues.apache.org/jira/browse/SUREFIRE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970093#comment-15970093 ] Brian Oxley commented on SUREFIRE-1359: --- Gack. I just tried again -- you are absolutely right. Yes, it complains about "corrupted stdin stream", but the exit code is 0. Thank you for pointing this out! I'd like to withdraw this issue. :) > 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)
[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file
[ https://issues.apache.org/jira/browse/SUREFIRE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970086#comment-15970086 ] Tibor Digana commented on SUREFIRE-1359: [~binkley] I used Maven 3.5.0. Can you reproduce it with the same version of Maven? > 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)
[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file
[
https://issues.apache.org/jira/browse/SUREFIRE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970085#comment-15970085
]
Tibor Digana commented on SUREFIRE-1359:
[~binkley]
Your attached report files do not have any failure and I made git clone of your
project and started the build {{mvn verify}}
{quote}
mvn verify
[WARNING] Source root doesn't exist:
d:\vcs\github\sproingk\target\generated-sources\annotations
[WARNING] Source root doesn't exist:
d:\vcs\github\sproingk\target\generated-test-sources\test-annotations
---
T E S T S
---
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
---
T E S T S
---
Running hm.binkley.labs.GitInfoIT
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/D:/.m2/repository/ch/qos/logback/logback-classic/1.1.11/logback-classic-1.1.11.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/D:/.m2/repository/org/slf4j/slf4j-jdk14/1.5.6/slf4j-jdk14-1.5.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type
[ch.qos.logback.classic.util.ContextSelectorStaticBinder]
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.997 sec - in
hm.binkley.labs.GitInfoIT
Running hm.binkley.labs.GreetingControllerIT
2017-04-15 21:09:31.536 WARN [bootstrap,,,] 21832 --- [ main]
o.s.c.n.a.ArchaiusAutoConfiguration : Netflix ConfigurationManager has
already been installed, unable to re-install
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.729 sec - in
hm.binkley.labs.GreetingControllerIT
Results :
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
{quote}
> 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)
[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file
[ https://issues.apache.org/jira/browse/SUREFIRE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969975#comment-15969975 ] Brian Oxley commented on SUREFIRE-1359: --- I'm happy to see the warning now appears in 2.20 that was hidden in 2.19.1. However, I still have the problem that the build fails in 2.20 but completes successfully in 2.19.1. > 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)
[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file
[
https://issues.apache.org/jira/browse/SUREFIRE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969287#comment-15969287
]
Tibor Digana commented on SUREFIRE-1359:
[~binkley]
Corrupted stream was even in {{2.19.1}} but was not visible in logs. In old
version this could crash or hang the build process.
The new version will warn you with {{Corrupted stdin stream in forked JVM}}
with each particular JVM# only once on the console.
These dump files should not crash your tests now but we are making them more
visible now.
We report them because this is not our fault and we want the vendors of another
libraries to fix it. The entire problem is that the libraries log to native
{{System.out}} caught on JVM startup, or direct stream {{FileDescriptor.out}}
within the forked JVM.
> 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)
[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file
[ https://issues.apache.org/jira/browse/SUREFIRE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15967792#comment-15967792 ] Brian Oxley commented on SUREFIRE-1359: --- I did some further differential testing. The `.mvn/jvm.config` file contains: ``` -Dorg.slf4j.simpleLogger.defaultLogLevel=WARN -Dorg.slf4j.simpleLogger.log.Sisu=WARN ``` I found that removing either line (or the whole file) let testing complete successfully. However, at the expense of maven being horribly noisy again. The reason I used that flag was the "Silence is Golden" rule: I don't want loud builds on success. > 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)
