Note that saveProgram initially catches this error and propagateErrorToWorkflow evidently finds a thread to send it to:

… org.jenkinsci.plugins.workflow.cps.CpsThread runNextChunk
FINE: runNextChunk on abnormal[java.io.NotSerializableException: SimpleClass]
… org.jenkinsci.plugins.workflow.cps.CpsThread runNextChunk
FINE: ran and produced error
java.io.NotSerializableException: SimpleClass
	at …

Yet this does not get put in the log, for whatever reason. It is only after several such occurrences that propagateErrorToWorkflow is run and does not have a thread to send the message to. Later I also see

… org.jenkinsci.plugins.workflow.cps.CpsStepContext getThread
FINE: no thread 2 among []
java.lang.IllegalStateException
	at org.jenkinsci.plugins.workflow.cps.CpsStepContext.getThread(CpsStepContext.java:219)
	at org.jenkinsci.plugins.workflow.cps.CpsStepContext$2.onSuccess(CpsStepContext.java:349)
	at org.jenkinsci.plugins.workflow.cps.CpsStepContext$2.onSuccess(CpsStepContext.java:343)
	at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$4$1.run(CpsFlowExecution.java:516)
	at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:32)
	at …

The StepEndNode with ID 11 (matching ExecutorStep) does have the correct ErrorAction. Yet the FlowEndNode (12) has result=FAILURE and no ErrorAction, which seems anomalous. WorkflowRun.finish did not print anything because it consults FlowExecution.getCauseOfFailure, which checks only the FlowEndNode for an ErrorAction. Perhaps CpsFlowExecution.onProgramEnd was being called with the wrong Outcome?

Change By: Jesse Glick (17/Mar/15 7:44 PM)
Assignee: Jesse Glick Kohsuke Kawaguchi
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to