java.lang.IllegalStateException: org.jenkinsci.plugins.workflow.steps.FlowInterruptedException

Google Groups | jgl...@cloudbees.com (JIRA) | 3 months ago
  1. 0

    [JIRA] (JENKINS-37730) DurableTaskStep.Execution hanging after process is dead

    Google Groups | 3 months ago | jgl...@cloudbees.com (JIRA)
    java.lang.IllegalStateException: org.jenkinsci.plugins.workflow.steps.FlowInterruptedException
  2. 0

    Found a case where a {{sh}} step ceased to produce more output in the middle of a command, for no apparent reason, and the build did not respond to normal abort. The virtual thread dump said {code:none} Thread #80 at DSL.sh(completed process (code -1) in /...@tmp/durable-... on ... (pid: ...)) at ... {code} But there is no active CPS VM thread, and nothing visibly happening on the agent, and all {{Timer}} threads are idle. So it seems that a call to {{check}} would have caused the step to fail—but perhaps none came? Possibly {{stop}} should do its own check for a non-null {{Controller.exitStatus}} and immediately fail in such a case (but we run the risk of delivering doubled-up events if {{check}} _does_ run later); or synchronously call {{check}} (though this runs the risk of having two such calls run simultaneously—it is not thread safe); or somehow reschedule it (same problem). At a minimum, the virtual thread dump should indicate what the current {{recurrencePeriod}} is. And the calls to {{schedule}} could save their {{ScheduledFuture}} results in a {{transient}} field, so we can check {{cancelled}} and {{done}} flags. Such diagnostics might make it clearer next time what actually happened. Also a {{term}} claimed to be terminating the {{sh}} step, but the build still did not finish. Again nothing in the physical thread dumps, and virtual thread dump still claims to be inside {{sh}}. System log showed {code:none} ... WARNING org.jenkinsci.plugins.workflow.cps.CpsStepContext onFailure already completed CpsStepContext[186]:Owner[...] java.lang.IllegalStateException: org.jenkinsci.plugins.workflow.steps.FlowInterruptedException at org.jenkinsci.plugins.workflow.cps.CpsStepContext.onFailure(CpsStepContext.java:325) at org.jenkinsci.plugins.workflow.job.WorkflowRun$5.onSuccess(WorkflowRun.java:300) at org.jenkinsci.plugins.workflow.job.WorkflowRun$5.onSuccess(WorkflowRun.java:296) at org.jenkinsci.plugins.workflow.support.concurrent.Futures$1.run(Futures.java:150) 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:702) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$5.onSuccess(CpsFlowExecution.java:689) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$4$1.run(CpsFlowExecution.java:626) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:32) 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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.jenkinsci.plugins.workflow.steps.FlowInterruptedException at org.jenkinsci.plugins.workflow.job.WorkflowRun.doTerm(WorkflowRun.java:295) at ... {code} So the program state seems to be somehow inconsistent as well; perhaps {{sh}} _did_ complete (it is not shown as in progress in flowGraphTable). Seems that the virtual thread dump needs some kind of fix TBD to better report the real state of a problematic program.

    Jenkins JIRA | 3 months ago | Jesse Glick
    java.lang.IllegalStateException: org.jenkinsci.plugins.workflow.steps.FlowInterruptedException
  3. 0

    GitHub comment 104#259943665

    GitHub | 3 weeks ago | jim-minter
    org.jenkinsci.plugins.workflow.steps.FlowInterruptedException
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    GitHub comment 104#259945254

    GitHub | 3 weeks ago | gabemontero
    org.jenkinsci.plugins.workflow.steps.FlowInterruptedException
  6. 0

    Compatability with parallel

    Google Groups | 2 months ago | Unknown author
    org.jenkinsci.plugins.workflow.steps.FlowInterruptedException

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. org.jenkinsci.plugins.workflow.steps.FlowInterruptedException

      No message provided

      at org.jenkinsci.plugins.workflow.job.WorkflowRun.doTerm()
    2. org.jenkinsci.plugins
      WorkflowRun.doTerm
      1. org.jenkinsci.plugins.workflow.job.WorkflowRun.doTerm(WorkflowRun.java:295)
      1 frame