You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (Jira)" <ji...@apache.org> on 2020/05/06 00:08:00 UTC
[jira] [Commented] (SUREFIRE-1629) Plugin crashes if tests are
forked and JPMS error occurs
[ https://issues.apache.org/jira/browse/SUREFIRE-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17100343#comment-17100343 ]
Tibor Digana commented on SUREFIRE-1629:
----------------------------------------
Let's fix all the JPMS issue in https://github.com/apache/maven-surefire/pull/293. We can discuss the solution on GH.
> Plugin crashes if tests are forked and JPMS error occurs
> --------------------------------------------------------
>
> Key: SUREFIRE-1629
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1629
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
> Affects Versions: 2.22.1
> Environment: OpenJDK 11.0.2
> Reporter: Gili
> Priority: Major
> Attachments: testcase.zip
>
>
> I tried running a test against an application with split packages and ended up with the following message in the {{dumpstream file}}:
> {code:java}
> # Created at 2019-01-25T16:20:23.856
> Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream 'Error occurred during initialization of boot layer'.
> java.lang.IllegalArgumentException: Stream stdin corrupted. Expected comma after third character in command 'Error occurred during initialization of boot layer'.
> at org.apache.maven.plugin.surefire.booterclient.output.ForkClient$OperationalData.<init>(ForkClient.java:507)
> at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.processLine(ForkClient.java:210)
> at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:177)
> at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:88)
> at java.base/java.lang.Thread.run(Thread.java:834)
> # Created at 2019-01-25T16:20:23.857
> Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream 'java.lang.LayerInstantiationException: Package com.foobar.internal.scope in both module com.foobar.database and module com.foobar.backend'.
> java.lang.IllegalArgumentException: Stream stdin corrupted. Expected comma after third character in command 'java.lang.LayerInstantiationException: Package com.foobar.internal.scope in both module com.foobar.database and module com.foobar.backend'.
> at org.apache.maven.plugin.surefire.booterclient.output.ForkClient$OperationalData.<init>(ForkClient.java:507)
> at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.processLine(ForkClient.java:210)
> at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:177)
> at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:88)
> at java.base/java.lang.Thread.run(Thread.java:834){code}
>
> Expected behavior: the Surefire plugin should surface this error message to stdout/stderr instead making developers dig into the dumpstream file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)