[ 
https://jira.codehaus.org/browse/SUREFIRE-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=313000#comment-313000
 ] 

Miguel Almeida commented on SUREFIRE-910:
-----------------------------------------

We also suffer from (apparently) random errors identical in our Jenkins server.

My suspicion is that it might be caused by memory errors, or issues with the 
database. The problem is always the same:
- fresh start on Jenkins has no issues
- few days later we get this error on the tests
- subsequent job runs yield the same error. Server restart "solves" it.

If I find anything relevant I'll post here.
                
> 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
>
> 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: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to