[JIRA] (JENKINS-30383) SynchronousNonBlockingStepExecution should allow restart of idempotent steps

5 views
Skip to first unread message

vincent@massol.net (JIRA)

unread,
Feb 24, 2018, 6:21:03 AM2/24/18
to jenkinsc...@googlegroups.com
Vincent Massol commented on Improvement JENKINS-30383
 
Re: SynchronousNonBlockingStepExecution should allow restart of idempotent steps

FTR just got the following on XWiki's CI:

...
[main] ➡ Build has failed, sending mails to concerned parties
[Pipeline] [main] emailext
Resuming build at Fri Feb 23 18:55:45 CET 2018 after Jenkins restart
Ready to run at Fri Feb 23 18:55:50 CET 2018
[Pipeline] [main] }
[Pipeline] [main] // stage
[Pipeline] [main] }
[Pipeline] [main] // node
[Pipeline] [main] }
[main] Failed in branch main
[Pipeline] // parallel
[Pipeline] }
[Pipeline] // stage
[Pipeline] End of Pipeline

GitHub has been notified of this commit’s build result

java.lang.Exception: Resume after a restart not supported for non-blocking synchronous steps
	at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution.onResume(AbstractSynchronousNonBlockingStepExecution.java:70)
	at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl$1.onSuccess(FlowExecutionList.java:185)
	at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl$1.onSuccess(FlowExecutionList.java:180)
	at com.google.common.util.concurrent.Futures$6.run(Futures.java:975)
	at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:253)
	at com.google.common.util.concurrent.ExecutionList$RunnableExecutorPair.execute(ExecutionList.java:149)
	at com.google.common.util.concurrent.ExecutionList.execute(ExecutionList.java:134)
	at com.google.common.util.concurrent.AbstractFuture.set(AbstractFuture.java:170)
	at com.google.common.util.concurrent.SettableFuture.set(SettableFuture.java:53)
	at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$5.onSuccess(CpsFlowExecution.java:835)
	at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$5.onSuccess(CpsFlowExecution.java:813)
	at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$4$1.run(CpsFlowExecution.java:746)
	at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:35)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
	at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Finished: FAILURE

The exception seems related.

You can see it live at http://ci.xwiki.org/job/XWiki/job/xwiki-platform/job/stable-9.11.x/74/console

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

mnrz57@gmail.com (JIRA)

unread,
Sep 12, 2019, 12:29:02 AM9/12/19
to jenkinsc...@googlegroups.com

What's the workaround for this issue? How can we get our job to work? They keep throwing this exception and they fail

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages