You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2019/08/03 14:37:15 UTC
[GitHub] [pulsar] zymap edited a comment on issue #4881: Update
pulsar-client-cpp README.md
zymap edited a comment on issue #4881: Update pulsar-client-cpp README.md
URL: https://github.com/apache/pulsar/pull/4881#issuecomment-517929080
The Jenkins always failed with this :
```
2019-08-03\T\13:24:06.727 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test (default-test) on project pulsar-broker: There are test failures.
2019-08-03\T\13:24:06.727 [ERROR]
2019-08-03\T\13:24:06.727 [ERROR] Please refer to /home/jenkins/jenkins-slave/workspace/pulsar_precommit_java8/pulsar-broker/target/surefire-reports for the individual test results.
2019-08-03\T\13:24:06.727 [ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
2019-08-03\T\13:24:06.728 [ERROR] ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
2019-08-03\T\13:24:06.728 [ERROR] Command was /bin/sh -c cd /home/jenkins/jenkins-slave/workspace/pulsar_precommit_java8/pulsar-broker && /usr/local/asfpackages/java/jdk1.8.0_191/jre/bin/java -Xmx2G -Dpulsar.allocator.pooled=false -Dpulsar.allocator.leak_detection=Advanced -Dlog4j.configurationFile=log4j2.xml -jar /home/jenkins/jenkins-slave/workspace/pulsar_precommit_java8/pulsar-broker/target/surefire/surefirebooter1867961874113362104.jar /home/jenkins/jenkins-slave/workspace/pulsar_precommit_java8/pulsar-broker/target/surefire 2019-08-03T11-47-15_552-jvmRun1 surefire5931702800715317106tmp surefire_2691214820909767404670tmp
2019-08-03\T\13:24:06.729 [ERROR] Error occurred in starting fork, check output in log
2019-08-03\T\13:24:06.729 [ERROR] Process Exit Code: 255
2019-08-03\T\13:24:06.729 [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
2019-08-03\T\13:24:06.729 [ERROR] Command was /bin/sh -c cd /home/jenkins/jenkins-slave/workspace/pulsar_precommit_java8/pulsar-broker && /usr/local/asfpackages/java/jdk1.8.0_191/jre/bin/java -Xmx2G -Dpulsar.allocator.pooled=false -Dpulsar.allocator.leak_detection=Advanced -Dlog4j.configurationFile=log4j2.xml -jar /home/jenkins/jenkins-slave/workspace/pulsar_precommit_java8/pulsar-broker/target/surefire/surefirebooter1867961874113362104.jar /home/jenkins/jenkins-slave/workspace/pulsar_precommit_java8/pulsar-broker/target/surefire 2019-08-03T11-47-15_552-jvmRun1 surefire5931702800715317106tmp surefire_2691214820909767404670tmp
2019-08-03\T\13:24:06.730 [ERROR] Error occurred in starting fork, check output in log
2019-08-03\T\13:24:06.730 [ERROR] Process Exit Code: 255
2019-08-03\T\13:24:06.730 [ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:511)
2019-08-03\T\13:24:06.731 [ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:458)
2019-08-03\T\13:24:06.731 [ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:299)
2019-08-03\T\13:24:06.731 [ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:247)
2019-08-03\T\13:24:06.731 [ERROR] at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1161)
2019-08-03\T\13:24:06.731 [ERROR] at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1002)
2019-08-03\T\13:24:06.732 [ERROR] at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:848)
2019-08-03\T\13:24:06.732 [ERROR] at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
2019-08-03\T\13:24:06.732 [ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
2019-08-03\T\13:24:06.732 [ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
2019-08-03\T\13:24:06.732 [ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
2019-08-03\T\13:24:06.732 [ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
2019-08-03\T\13:24:06.733 [ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
2019-08-03\T\13:24:06.733 [ERROR] at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
2019-08-03\T\13:24:06.733 [ERROR] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
2019-08-03\T\13:24:06.733 [ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
2019-08-03\T\13:24:06.733 [ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
2019-08-03\T\13:24:06.734 [ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
2019-08-03\T\13:24:06.734 [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
2019-08-03\T\13:24:06.734 [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
2019-08-03\T\13:24:06.734 [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:192)
2019-08-03\T\13:24:06.734 [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2019-08-03\T\13:24:06.734 [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2019-08-03\T\13:24:06.735 [ERROR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2019-08-03\T\13:24:06.735 [ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
2019-08-03\T\13:24:06.735 [ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
2019-08-03\T\13:24:06.735 [ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
2019-08-03\T\13:24:06.735 [ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
2019-08-03\T\13:24:06.735 [ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
2019-08-03\T\13:24:06.736 [ERROR] Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
2019-08-03\T\13:24:06.736 [ERROR] Command was /bin/sh -c cd /home/jenkins/jenkins-slave/workspace/pulsar_precommit_java8/pulsar-broker && /usr/local/asfpackages/java/jdk1.8.0_191/jre/bin/java -Xmx2G -Dpulsar.allocator.pooled=false -Dpulsar.allocator.leak_detection=Advanced -Dlog4j.configurationFile=log4j2.xml -jar /home/jenkins/jenkins-slave/workspace/pulsar_precommit_java8/pulsar-broker/target/surefire/surefirebooter1867961874113362104.jar /home/jenkins/jenkins-slave/workspace/pulsar_precommit_java8/pulsar-broker/target/surefire 2019-08-03T11-47-15_552-jvmRun1 surefire5931702800715317106tmp surefire_2691214820909767404670tmp
2019-08-03\T\13:24:06.737 [ERROR] Error occurred in starting fork, check output in log
2019-08-03\T\13:24:06.737 [ERROR] Process Exit Code: 255
2019-08-03\T\13:24:06.737 [ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:670)
2019-08-03\T\13:24:06.737 [ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.access$600(ForkStarter.java:116)
2019-08-03\T\13:24:06.737 [ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter$2.call(ForkStarter.java:445)
2019-08-03\T\13:24:06.738 [ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter$2.call(ForkStarter.java:421)
2019-08-03\T\13:24:06.738 [ERROR] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
2019-08-03\T\13:24:06.738 [ERROR] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
2019-08-03\T\13:24:06.738 [ERROR] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
2019-08-03\T\13:24:06.738 [ERROR] at java.lang.Thread.run(Thread.java:748)
2019-08-03\T\13:24:06.738 [ERROR] -> [Help 1]
2019-08-03\T\13:24:06.739 [ERROR]
2019-08-03\T\13:24:06.739 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
2019-08-03\T\13:24:06.739 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
2019-08-03\T\13:24:06.739 [ERROR]
2019-08-03\T\13:24:06.739 [ERROR] For more information about the errors and possible solutions, please read the following articles:
2019-08-03\T\13:24:06.739 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
2019-08-03\T\13:24:06.740 [ERROR]
2019-08-03\T\13:24:06.740 [ERROR] After correcting the problems, you can resume the build with the command
2019-08-03\T\13:24:06.740 [ERROR] mvn <goals> -rf :pulsar-broker
Build step 'Invoke top-level Maven targets' marked build as failure
Archiving artifacts
Recording test results
Setting status of 195870071ea2f67d106b4e88dd3405a536c3d606 to FAILURE with url https://builds.apache.org/job/pulsar_precommit_java8/10605/ and message: 'FAILURE
'
Using context: Jenkins: Java 8 - Unit Tests
Finished: FAILURE
```
And I found the same question on the maven surefire plugin FAQ: https://maven.apache.org/surefire/maven-surefire-plugin/faq.html
Surefire does not support tests or any referenced libraries calling System.exit() at any time. If they do so, they are incompatible with Surefire and you should probably file an issue with the library/vendor. Alternatively the forked VM could also have crashed for a number of reasons. Look for the classical "hs_err*" files indicating VM crashes or examine the Maven log output when the tests execute. Some "extraordinary" output from crashing processes may be dumped to the console/log. If this happens on a CI environment and only after it runs for some time, there is a fair chance your test suite is leaking some kind of OS-level resource that makes things worse at every run. Regular OS-level monitoring tools may give you some indication.
So is there any ways to reduce the phenomenon?
@sijie
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services