[JIRA] (JENKINS-33761) Ability to disable Pipeline durability and "resume" build.
Title: Message Title
Nick Jones edited a comment on JENKINS-33761
Re: Ability to disable Pipeline durability and "resume" build.
I've just experienced the "Creating placeholder flownodes because failed loading originals." error with this stack trace on a Jenkins system running workflow-job 2.25 and workflow-cps 2.64:{code:java}java.io.IOException: Tried to load head FlowNodes for execution Owner[Redacted/dev/3:Redacted/dev #3] but FlowNode was not found in storage for head id:FlowNodeId 1:59 at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:678) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:715) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:875) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:745) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:501) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:483) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:381) at hudson.model.RunMap.getById(RunMap.java:205) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.run(WorkflowRun.java:1112) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:1123) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:65) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:57) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl.onLoaded(FlowExecutionList.java:178) at jenkins.model.Jenkins.(Jenkins.java:989) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233)Finished: FAILURE{code}Restarting the job manually appears to have resolved it, but is there additional information I can provide to troubleshoot what might have caused this? Or is this a different issue than what's discussed here? Edit: I should add that workflow-cps was upgraded from 2.63 to 2.64 between the last successful job and the one that failed with the stack trace above. Workflow-job was not changed.
Add Comment
[JIRA] (JENKINS-33761) Ability to disable Pipeline durability and "resume" build.
Title: Message Title Nick Jones commented on JENKINS-33761 Re: Ability to disable Pipeline durability and "resume" build. I've just experienced the "Creating placeholder flownodes because failed loading originals." error with this stack trace on a Jenkins system running workflow-job 2.25 and workflow-cps 2.64: java.io.IOException: Tried to load head FlowNodes for execution Owner[Redacted/dev/3:Redacted/dev #3] but FlowNode was not found in storage for head id:FlowNodeId 1:59 at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:678) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:715) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:875) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:745) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:501) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:483) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:381) at hudson.model.RunMap.getById(RunMap.java:205) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.run(WorkflowRun.java:1112) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:1123) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:65) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:57) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl.onLoaded(FlowExecutionList.java:178) at jenkins.model.Jenkins.(Jenkins.java:989) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233) Finished: FAILURE Restarting the job manually appears to have resolved it, but is there additional information I can provide to troubleshoot what might have caused this? Or is this a different issue than what's discussed here? Add Comment
[JIRA] (JENKINS-33761) Ability to disable Pipeline durability and "resume" build.
Title: Message Title
Russell Gallop commented on JENKINS-33761
Re: Ability to disable Pipeline durability and "resume" build.
Thread dump from a node this is happening on attached. Jenkins 2.107.3 Pipeline 2.5 Pipeline API 2.27 Pipeline Nodes and Processes 2.19 Pipeline Step API 2.15 JENKINS-33671_thread_dump.txt Oddly, having killed the job from "Build Executor Status" the node is freed up but the job seems to still think it is running:
[Pipeline] {
Creating placeholder flownodes because failed loading originals.
Resuming build at Thu Sep 20 11:47:46 BST 2018 after Jenkins restart
[Pipeline] End of Pipeline
Finished: FAILURE
The next thing that this would be doing would be retry { checkout git ... }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33761) Ability to disable Pipeline durability and "resume" build.
Title: Message Title Russell Gallop updated an issue Jenkins / JENKINS-33761 Ability to disable Pipeline durability and "resume" build. Change By: Russell Gallop Attachment: JENKINS-33671_thread_dump.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33761) Ability to disable Pipeline durability and "resume" build.
Title: Message Title Russell Gallop commented on JENKINS-33761 Re: Ability to disable Pipeline durability and "resume" build. We have seen the same thing. Resume definitely disabled and still causing hangs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33761) Ability to disable Pipeline durability and "resume" build.
Title: Message Title Roy Arnon commented on JENKINS-33761 Re: Ability to disable Pipeline durability and "resume" build. Hello, I am not sure this is related to this issue, but in our pipeline build job we recently added the disableResume step and it does not seem to work correctly: Jenkins 2.89.3 Pipeline 2.5 Pipeline API 2.27 Pipeline Nodes and Processes 2.20 Pipeline Step API 2.16 Scripts Security 1.44 durabilityHint=PERFORMANCE_OPTIMIZED org.jenkinsci.plugins.workflow.job.properties.DisableResumeJobProperty Groovy Sandbox = disabled Creating placeholder flownodes because failed loading originals. Resuming build at Thu Aug 30 12:42:45 UTC 2018 after Jenkins restart [Bitbucket] Notifying pull request build result [Bitbucket] Build result notified [lockable-resources] released lock on [UNIT_TEST_RESOURCE_3] java.io.IOException: Tried to load head FlowNodes for execution Owner[Products.Pipeline/PR-5615/7:Products.Pipeline/PR-5615 #7] but FlowNode was not found in storage for head id:FlowNodeId 1:586 at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:678) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:715) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:875) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:745) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:500) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:482) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:380) at hudson.model.RunMap.getById(RunMap.java:205) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.run(WorkflowRun.java:1098) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:1109) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:65) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:57) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl.onLoaded(FlowExecutionList.java:178) at jenkins.model.Jenkins.(Jenkins.java:974) at hudson.model.Hudson.(Hudson.java:86) at hudson.model.Hudson.(Hudson.java:82) at hudson.WebAppMain$3.run(WebAppMain.java:233) Finished: SUCCESS This is an issue for us as the build was marked as SUCCESS in bitbucket, which allowed a user to merge a failing test into our release branch. The job was definitely running with resume disabled, as this was printed at start of job: Resume disabled by user, switching to high-performance, low-durability mode. Any ideas?
[JIRA] (JENKINS-33761) Ability to disable Pipeline durability and "resume" build.
Title: Message Title
Mike Kozell edited a comment on JENKINS-33761
Re: Ability to disable Pipeline durability and "resume" build.
[~svanoort]After upgrading Jenkins with the following, I was not able to reproduce the issue after a build timeout, cancelling a build, and restarting Jenkins in the middle of a build.Jenkins 2.89.4Pipeline 2.5Pipeline API 2.26Pipeline Nodes and Processes 2.19Pipeline Step API 2.14Scripts Security 1.41durabilityHint=PERFORMANCE_OPTIMIZEDorg.jenkinsci.plugins.workflow.job.properties.DisableResumeJobPropertyGroovy Sandbox = disabledJava = 1.8.0_162Although my jobs correctly didn't resume after Jenkins restart, I did see the message below in the build logs. {code:java} Resuming build at Sat Feb 24 06:38:10 UTC 2018 after Jenkins restart[Pipeline] End of Pipelinejava.io.IOException: Cannot resume build -- – was not cleanly saved when Jenkins shut down. {code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33761) Ability to disable Pipeline durability and "resume" build.
Title: Message Title Mike Kozell commented on JENKINS-33761 Re: Ability to disable Pipeline durability and "resume" build. Sam Van Oort After upgrading Jenkins with the following, I was not able to reproduce the issue after a build timeout, cancelling a build, and restarting Jenkins in the middle of a build. Jenkins 2.89.4 Pipeline 2.5 Pipeline API 2.26 Pipeline Nodes and Processes 2.19 Pipeline Step API 2.14 Scripts Security 1.41 durabilityHint=PERFORMANCE_OPTIMIZED org.jenkinsci.plugins.workflow.job.properties.DisableResumeJobProperty Groovy Sandbox = disabled Java = 1.8.0_162 Although my jobs correctly didn't resume after Jenkins restart, I did see the message below in the build logs. Resuming build at Sat Feb 24 06:38:10 UTC 2018 after Jenkins restart [Pipeline] End of Pipeline java.io.IOException: Cannot resume build – was not cleanly saved when Jenkins shut down. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33761) Ability to disable Pipeline durability and "resume" build.
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-33761 Ability to disable Pipeline durability and "resume" build. Change By: Sam Van Oort Labels: project-cheetah Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
