Jenkins: Cannot resume build because FlowNode 23 for FlowHead 1 could not be loaded.
Summary
Observed Jenkins build failures with
ERROR: Cannot resume build because FlowNode 23 for FlowHead 1 could not be loaded. This is expected to happen when using the PERFORMANCE_OPTIMIZED durability setting and Jenkins is not shut down cleanly. Consider investigating to understand if Jenkins was not shut down cleanly or switching to the MAX_SURVIVABILITY durability setting which should prevent this issue in most cases.Steps to reproduce
Can't so far.
I've rebuilt some jobs and they seem fine now.
Perhaps the occurrences were time-related rather than anything else-related.
Reporting for visibility/tracking/historical reasons.
Feel free to close w/o action if this is single case.
What is the current bug behavior?
Build is not completed successfully.
What is the expected correct behavior?
Build is completed successfully.
Relevant logs and/or screenshots
- https://ci.eclipse.org/openmq/job/openmq-build-and-test-using-jenkinsfile/job/master/1363/console
- https://ci.eclipse.org/openmq/job/openmq-sonarqube-using-jenkinsfile-for-pr/job/master/30/console
- https://ci.eclipse.org/openmq/job/openmq-sonarqube-using-jenkinsfile-for-pr/view/change-requests/job/PR-2405/2/console
Priority
- Urgent
- High
- Medium
- Low
Severity
- Blocker
- Major
- Normal
- Low
Impact
Small inconvenience, as manual intervention to inspect failure reason and re-trigger build is required.
Activity
- could be related: #4596
added IT-prioritylow IT-severitylow service:CI statewip team:releng labels
assigned to @pstankie
@pygieo Yes, this is about durability jenkins setting, which we have by default set in global jenkins for performance
PERFORMANCE_OPTIMIZED. You can change it if Jenkinsfile with:options { durabilityHint 'PERFORMANCE_OPTIMIZED' }Unless this is not critical we can leave it as it is, since jobs are short, but If you want you can change it in Jenkinsfile(s).
removed statewip label
