[
https://jira.codehaus.org/browse/SUREFIRE-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=330467#comment-330467
]
Hung Huynh commented on SUREFIRE-910:
-------------------------------------
My project has 300+ unit tests that exercising quite a lot of 3rd party
libraries. We're using Jenkins for CI. Now that the Jenkins job is failing with
this error without an obvious JUnit report saying which test has failed. The
console log is quite long and there is no obvious way to pinpoint which test is
causing the problem. Before upgrading to surefire 2.15, there is at least a
JUnit report with zero in length, but from the filename, we could at least
deduct the test class name.
Would it be possible to tell which test is causing the error from surefire code
and print that out to surefire report?
> Surefire 2.12.1 fails with "The forked VM terminated without saying properly
> goodbye"
> -------------------------------------------------------------------------------------
>
> Key: SUREFIRE-910
> URL: https://jira.codehaus.org/browse/SUREFIRE-910
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Reporter: Ilya Katsov
> Assignee: Kristian Rosenvold
> Fix For: 2.13
>
>
> Build fails with "The forked VM terminated without saying properly goodbye"
> message with no information about the source of the problem:
> {code}
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.125 sec
> Running org.apache.hadoop.fs.viewfs.TestViewFsHdfs
> Tests run: 42, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.149 sec
> Running org.apache.hadoop.fs.TestFcHdfsSymlink
> Tests run: 67, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 20.792 sec
> Results :
> Tests run: 1033, Failures: 0, Errors: 0, Skipped: 1
> [INFO]
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Skipping Apache Hadoop HDFS Project
> [INFO] This project has been banned from the build due to previous failures.
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Skipping Apache Hadoop HDFS
> [INFO] This project has been banned from the build due to previous failures.
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Hadoop HDFS ................................ FAILURE
> [1:06:10.415s]
> [INFO] Apache Hadoop HttpFS .............................. SKIPPED
> [INFO] Apache Hadoop HDFS Project ........................ SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 1:06:11.188s
> [INFO] Finished at: Wed Sep 05 12:01:46 MSK 2012
> [INFO] Final Memory: 24M/394M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.12.1:test (default-test) on
> project hadoop-hdfs: ExecutionException; nested exception is
> java.util.concurrent.ExecutionException: java.lang.RuntimeException: The
> forked VM terminated without saying properly goodbye. VM crash or System.exit
> called ? -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-surefire-plugin:2.12.1:test
> (default-test) on project hadoop-hdfs: ExecutionException; nested exception
> is java.util.concurrent.ExecutionException: java.lang.RuntimeException: The
> forked VM terminated without saying properly goodbye. VM crash or System.exit
> called ?
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> 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:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> {code}
> It seems to be similar to SUREFIRE-837, but it is not fixed 2.12.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
