You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Seweryn Habdank-Wojewodzki (JIRA)" <ji...@apache.org> on 2017/05/02 08:47:04 UTC
[jira] [Comment Edited] (SUREFIRE-1368) Not very informative fatal
exit from testing - missing quotation in generated execution command
[ https://issues.apache.org/jira/browse/SUREFIRE-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15992545#comment-15992545 ]
Seweryn Habdank-Wojewodzki edited comment on SUREFIRE-1368 at 5/2/17 8:46 AM:
------------------------------------------------------------------------------
[~tibor17] for the version 2.20 there is no problem with version printing.
It was stated in my comment :-) :
https://issues.apache.org/jira/browse/SUREFIRE-1368?focusedCommentId=15988528&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15988528
Thanks that you consider improvements in error reporting. I really appreciate your attitude.
As you stated you can check existence of the system property or existence of the target path, so error would look like:
"Error: path '{jdk180.path}\bin\java' does not exists" or something like that :-).
was (Author: habdank):
[~tibor17] for the version 2.20 there is no problem with version printing.
It was stated in my comment :-) :
https://issues.apache.org/jira/browse/SUREFIRE-1368?focusedCommentId=15988528&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15988528
Thanks that you consider improvements in error reporting. I really appreciate you attitude.
As you stated you can check existence of the system property or existence of the target path, so error would look like:
"Error: path '{jdk180.path}\bin\java' does not exists" or something like that :-).
> Not very informative fatal exit from testing - missing quotation in generated execution command
> -----------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-1368
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1368
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.15, 2.19.1
> Environment: Windows 10
> Reporter: Seweryn Habdank-Wojewodzki
> Assignee: Tibor Digana
>
> Dears,
> I am starting build {{mvn -X -e clean install}} which includes test written using TestNG framework v. 6.8.8.
> There comes following information:
> {noformat}
> [INFO] --- maven-surefire-plugin:2.15:test (default-test) @ logviewerservice-test ---
> [INFO] Surefire report directory: C:\StorageSpace\Projects\clj_project\logviewerservice-master\logviewerservice-test\target\surefire-reports
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Das System kann den angegebenen Pfad nicht finden.
> Results :
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> ...
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.15:test (default-test) on project logviewerservice-test: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.15:test failed: The forked VM terminated without saying properly goodbye. VM crash or System.exit called ?
> {noformat}
> The "Das System kann den angegebenen Pfad nicht finden." means, that given system path cannot be found.
> 1. Why mvn uses console language and not English?
> 2. Error message does not state which path cannot be found, so it makes impossible to solve the problem, as testing uses many different paths.
> 3. Everything happend before even target/surefire-reports directory is created.
> Can you help with that issue?
> The configuration is simple:
> {code:xml}
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-surefire-plugin</artifactId>
> <version>2.19.1</version>
> </plugin>
> {code}
> What is ofcourse interesting, why v. 2.19.1 appears to be v. 2.15 in build.
> Errors and exceptions are below:
> {noformat}
> [DEBUG] boot(compact) classpath: surefire-booter-2.15.jar surefire-api-2.15.jar test-classes classes
> ... (bunch of jars)
> surefire-testng-utils-2.15.jar surefire-grouper-2.15.jar surefire-testng-2.15.jar common-java5-2.15.jar
> Forking command line: cmd.exe /X /C "${jdk180.path}\bin\java "-Djava.library.path=C:/Program Files (x86)/Foo/DLL" -jar C:\StorageSpace\Projects\my-project\target\surefire\surefirebooter3832366471835279317.jar C:\StorageSpace\Projects\my-project\target\surefire\surefire9145576077183878807tmp C:\StorageSpace\Projects\my-project\target\surefire\surefire_0107990010860156596tmp"
> Das System kann den angegebenen Pfad nicht finden.
> [ERROR] Command wascmd.exe /X /C "${jdk180.path}\bin\java "-Djava.library.path=C:/Program Files (x86)/Foo/DLL" -jar C:\StorageSpace\Projects\my-project\target\surefire\surefirebooter3832366471835279317.jar C:\StorageSpace\Projects\my-project\target\surefire\surefire9145576077183878807tmp C:\StorageSpace\Projects\my-project\target\surefire\surefire_0107990010860156596tmp"
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.15:test (default-test) on project myservice-test: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.15:test failed: The forked VM terminated without saying properly goodbye. VM crash or System.exit called ?
> Command wascmd.exe /X /C "${jdk180.path}\bin\java "-Djava.library.path=C:/Program Files (x86)/Foo/DLL" -jar C:\StorageSpace\Projects\my-project\target\surefire\surefirebooter3832366471835279317.jar C:\StorageSpace\Projects\my-project\target\surefire\surefire9145576077183878807tmp C:\StorageSpace\Projects\my-project\target\surefire\surefire_0107990010860156596tmp"
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.15:test failed: The forked VM terminated without saying properly goodbye. VM crash or System.exit called ?
> Command wascmd.exe /X /C "${jdk180.path}\bin\java "-Djava.library.path=C:/Program Files (x86)/Foo/DLL" -jar C:\StorageSpace\Projects\my-project\target\surefire\surefirebooter3832366471835279317.jar C:\StorageSpace\Projects\my-project\target\surefire\surefire9145576077183878807tmp C:\StorageSpace\Projects\my-project\target\surefire\surefire_0107990010860156596tmp"
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 20 more
> Caused by: java.lang.RuntimeException: The forked VM terminated without saying properly goodbye. VM crash or System.exit called ?
> Command wascmd.exe /X /C "${jdk180.path}\bin\java "-Djava.library.path=C:/Program Files (x86)/Foo/DLL" -jar C:\StorageSpace\Projects\my-project\target\surefire\surefirebooter3832366471835279317.jar C:\StorageSpace\Projects\my-project\target\surefire\surefire9145576077183878807tmp C:\StorageSpace\Projects\my-project\target\surefire\surefire_0107990010860156596tmp"
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:485)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:352)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:158)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:883)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:747)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:645)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)