[JIRA] (JENKINS-54105) Maven Event Spy InterruptedException

Maven Event Spy InterruptedException

Issue Type:	Improvement
Assignee:	Alvaro Lobato
Components:	pipeline-maven-plugin
Created:	2018-10-16 14:30
Environment:	Jenkins 2.138.2
Priority:	Minor
Reporter:	Vincent Massol

Reporting error as indicated in the pipeline logs:

 
                                                                ERROR: [withMaven] WARNING Exception processing the logs generated by the Jenkins Maven Event Spy /home/hudsonagent/jenkins_root/workspace/XWiki_xwiki-platform_master-ZGNMAWOYB6APYNMYWF7HH475RM4M6C6RE2U76Y5M5RWNQJWOLFGA@tmp/withMavenaa64a854/maven-spy-20181016-112527-9765838541643520342520.log, ignore file.  Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org
java.lang.InterruptedException
        at java.lang.Object.wait(Native Method)
        at hudson.remoting.Request.call(Request.java:177)
        at hudson.remoting.Channel.call(Channel.java:954)
        at hudson.FilePath.act(FilePath.java:1071)
        at hudson.FilePath.act(FilePath.java:1060)
        at hudson.FilePath.exists(FilePath.java:1580)
        at org.jenkinsci.plugins.pipeline.maven.publishers.DependenciesFingerprintPublisher.process(DependenciesFingerprintPublisher.java:160)
        at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:118)
        at org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution$WithMavenStepExecutionCallBack.finished(WithMavenStepExecution.java:1053)
        at org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$TailCall.onSuccess(BodyExecutionCallback.java:114)
        at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.receive(CpsBodyExecution.java:368)
        at com.cloudbees.groovy.cps.impl.ValueBoundContinuation.receive(ValueBoundContinuation.java:21)
        at com.cloudbees.groovy.cps.Block$Noop.eval(Block.java:30)
        at com.cloudbees.groovy.cps.Next.step(Next.java:83)
        at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174)
        at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)
        at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122)
        at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261)
        at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)
        at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$101(SandboxContinuable.java:34)
        at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.lambda$run0$0(SandboxContinuable.java:59)
        at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108)
        at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:58)
        at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:182)
        at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:332)
        at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:83)
        at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:244)
        at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:232)
        at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131)
        at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
 
                                                            

Thanks

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

vincent@massol.net (JIRA)

unread,

Oct 16, 2018, 10:33:01 AM10/16/18

to jenkinsc...@googlegroups.com

Vincent Massol commented on

FWIW this is the error we had in https://ci.xwiki.org/job/XWiki/job/xwiki-platform/job/master/1065/ (will be removed in the near future though).

vincent@massol.net (JIRA)

unread,

Oct 16, 2018, 10:34:02 AM10/16/18

to jenkinsc...@googlegroups.com

Vincent Massol commented on

Actually seems it's similar to https://issues.jenkins-ci.org/browse/JENKINS-48283 which is still open

cleclerc@cloudbees.com (JIRA)

unread,

Oct 29, 2018, 5:44:04 AM10/29/18

to jenkinsc...@googlegroups.com

Cyrille Le Clerc commented on

3.5.15 adds messages to help understand the problem:

In case of InterruptedException, a message in the logs with the duration since the beginning of the processing is outputted, we want to verify if we have reached the standard timeout of the pipeline steps:

 
                                                                [withMaven] Processing of Maven build outputs interrupted in " + mavenPublisher.toString() + " after " +
                                    TimeUnit.MILLISECONDS.convert(System.nanoTime() - nanosBefore, TimeUnit.NANOSECONDS) + "ms.

When INFO level is enabled on org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor, a summary of the duration of each publisher is added to the build logs. Sample:

[withMaven] Publishers: Generated Artifacts Publisher: 36 ms, Junit Publisher: 9 ms, Dependencies Fingerprint Publisher: 6 ms, Pipeline Graph Publisher: 1 ms, Open Task Scanner Publisher: 25 ms

cleclerc@cloudbees.com (JIRA)

unread,

Oct 29, 2018, 5:45:02 AM10/29/18

to jenkinsc...@googlegroups.com

Cyrille Le Clerc edited a comment on