-
Bug
-
Resolution: Unresolved
-
Major
-
None
Since a few days, our builds regularly fail with an OOM:
ERROR: [withMaven] WARNING Exception executing Maven reporter 'Junit Publisher' / org.jenkinsci.plugins.pipeline.maven.publishers.JunitTestsPublisher. Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org java.io.IOException: Remote call on JNLP4-connect connection from jenkins-worker07.xxx.yyy/Z.Z.Z.Z:ZZZZZ failed at hudson.remoting.Channel.call(Channel.java:1007) at com.google.jenkins.flakyTestHandler.plugin.JUnitFlakyTestDataPublisher.contributeTestData(JUnitFlakyTestDataPublisher.java:57) at hudson.tasks.junit.JUnitResultArchiver.parseAndSummarize(JUnitResultArchiver.java:292) at org.jenkinsci.plugins.pipeline.maven.publishers.JUnitUtils.archiveResults(JUnitUtils.java:87) at org.jenkinsci.plugins.pipeline.maven.publishers.JunitTestsPublisher.executeReporter(JunitTestsPublisher.java:373) at org.jenkinsci.plugins.pipeline.maven.publishers.JunitTestsPublisher.process(JunitTestsPublisher.java:212) at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:172) at org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution2$WithMavenStepExecutionCallBack.finished(WithMavenStepExecution2.java:1303) at org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution$TailCall.lambda$onSuccess$0(GeneralNonBlockingStepExecution.java:140) at org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution.lambda$run$0(GeneralNonBlockingStepExecution.java:77) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: java.lang.OutOfMemoryError: Java heap space
Although increasing the heap would probably (temporarily) mitigate the problem, we cannot do this due to resource limitation.
Deactivating the flaky-test-handler-plugin fixes the problem.
I expect that this plugin has a similar memory footprint than regular test case reporting.