Problems with https://ci.eclipse.org/oomph
Summary
This build failed with this error:
https://ci.eclipse.org/oomph/job/git-indexer/80/console
Creating placeholder flownodes because failed loading originals. ERROR: Cannot resume build because FlowNode 61 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
These builds are failing more often than not:
https://ci.eclipse.org/oomph/job/build/job/master/
The final stage fails like this:
[Checks API] No suitable checks publisher found. [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Promote) Stage "Promote" skipped due to earlier failure(s) [Pipeline] getContext [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Declarative: Post Actions) [Pipeline] emailext Sending email to: ed.merks@gmail.com [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // timeout [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Also: org.jenkinsci.plugins.workflow.actions.ErrorAction$ErrorId: 6437be03-1eb9-475b-8b1e-daa0a0ad0bd0 org.jenkinsci.plugins.workflow.steps.SynchronousResumeNotSupportedException: Resume after a restart not supported for non-blocking synchronous steps at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.onResume(SynchronousNonBlockingStepExecution.java:75) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList
ParallelResumer.lambda
run$5(FlowExecutionList.java:420) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68) at jenkins.util.ErrorLoggingExecutorService.lambda$wrap$0(ErrorLoggingExecutorService.java:51) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at java.base/java.lang.Thread.run(Thread.java:857)
A good build just continues:
[Checks API] No suitable checks publisher found. [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Promote) [Pipeline] node Running on promotion-vm in /opt/public/hipp/homes/genie.oomph/workspace/build_master [Pipeline] { [Pipeline] checkout The recommended git tool is: git using credential github-bot Cloning the remote Git repository Cloning with configured refspecs honoured and without tags Cloning repository https://github.com/eclipse-oomph/oomph.git
git init /opt/public/hipp/homes/genie.oomph/workspace/build_master # timeout=10 Fetching upstream changes from https://github.com/eclipse-oomph/oomph.git git --version # timeout=10 git --version # 'git version 2.27.0' using GIT_ASKPASS to set credentials GitHub bot (username/token) git fetch --no-tags --force --progress -- https://github.com/eclipse-oomph/oomph.git +refs/heads/master:refs/remotes/origin/master # timeout=10 git config remote.origin.url https://github.com/eclipse-oomph/oomph.git # timeout=10 git config --add remote.origin.fetch +refs/heads/master:refs/remotes/origin/master # timeout=10 Avoid second fetch Checking out Revision 0b7f3b0fed9611756d917e47989d7018d73fce91 (master) git config core.sparsecheckout # timeout=10 git checkout -f 0b7f3b0fed9611756d917e47989d7018d73fce91 # timeout=10 Commit message: "Contribute preliminary NatTable setup"
So it looks like it's failing to start the stage on the promotion-vm.
Maybe just restarting the ci.instance will be helpful? Both builds should be trigger overnight...
Priority
-
Urgent - [2] High
-
Medium -
Low
Severity
-
Blocker -
Major -
Normal -
Low
Impact
I must build M1 this week and this is likely to be a significant issue.