Skip to content

Console Output

Started by timer
 > git rev-parse --resolve-git-dir /var/jenkins/caches/git-8ddd5da576d032700dc6cbf1b4f3260e/.git # timeout=10
Setting origin to https://github.com/eclipse/swtchart.git
 > git config remote.origin.url https://github.com/eclipse/swtchart.git # timeout=10
Fetching origin...
Fetching upstream changes from origin
 > git --version # timeout=10
 > git --version # 'git version 2.43.0'
 > git config --get remote.origin.url # timeout=10
 > git fetch --tags --force --progress -- origin +refs/heads/*:refs/remotes/origin/* # timeout=10
Seen branch in repository origin/0.7.x
Seen branch in repository origin/0.8.0
Seen branch in repository origin/0.8.1
Seen branch in repository origin/0.8.x
Seen branch in repository origin/REL-0.12.0
Seen branch in repository origin/REL-0.13.0
Seen branch in repository origin/REL-0.14.0
Seen branch in repository origin/REL-0.7.0
Seen branch in repository origin/develop
Seen branch in repository origin/master
Seen 10 remote branches
Obtained Jenkinsfile from bb1ff0fe80498694b5c79a9df74a937a55839411
[Pipeline] Start of Pipeline
[Pipeline] echo
[WARNING] label option is deprecated. To use a static pod template, use the 'inheritFrom' option.
[Pipeline] podTemplate
[Pipeline] {
[Pipeline] node
Still waiting to schedule task
Waiting for next available executor on ‘centos-7-s53p3Creating placeholder flownodes because failed loading originals.
ERROR: Cannot resume build because FlowNode 6 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.
Finished: FAILURE