You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Pavel_K (Jira)" <ji...@apache.org> on 2020/04/25 11:22:00 UTC
[jira] [Commented] (SUREFIRE-1780) Print JPMS errors from native
stream of the fork JVM
[ https://issues.apache.org/jira/browse/SUREFIRE-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17092185#comment-17092185 ]
Pavel_K commented on SUREFIRE-1780:
-----------------------------------
[~tibordigana] I have seen that you fixed this issue, so I've cloned the project from github, built it and now try to run my test this way:
{code:java}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>3.0.0-SNAPSHOT</version>
<configuration>
</configuration>
</plugin>
{code}
I get this
{code:java}
Command was /bin/sh -c cd /home/pavel/Temp/surefire-jpms/com.foo.plugin && /opt/jdk-14/bin/java @/home/pavel/Temp/surefire-jpms/com.foo.plugin/target/surefire/surefireargs1141888352115027119 /home/pavel/Temp/surefire-jpms/com.foo.plugin/target/surefire 2020-04-25T14-15-05_097-jvmRun1 surefire16724086776763298357tmp surefire_04817899869263360950tmp
Error occurred in starting fork, check output in log
Process Exit Code: 1
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork (ForkStarter.java:748)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run (ForkStarter.java:305)
{code}
But the problem is there is no surefire folder in target:
{code:java}
pavel@pc1:~/Temp/surefire-jpms/com.foo.plugin/target$ pwd
/home/pavel/Temp/surefire-jpms/com.foo.plugin/target
pavel@pc1:~/Temp/surefire-jpms/com.foo.plugin/target$ ls
classes generated-sources generated-test-sources maven-status test-classes
{code}
Do I do something wrong?
> Print JPMS errors from native stream of the fork JVM
> ----------------------------------------------------
>
> Key: SUREFIRE-1780
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1780
> Project: Maven Surefire
> Issue Type: Improvement
> Components: process forking
> Environment: Java 9+
> Reporter: Tibor Digana
> Assignee: Tibor Digana
> Priority: Major
> Fix For: 3.0.0-M5
>
>
> When JVM prints own logs to the native stream, the surefire stream becomes corrupted. These are printed in a dump file and they are supposed a stream corruption. We can extract some special logs from this corrupted stream.
> This issue is based on the last discussion in SUREFIRE-1262.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)