Some jobs spend a lot of time in "Spin up environment"


#1

Hi!

Since yesterday we’re seeing some random jobs spending a lot of time to spin up environment. See this workflow, for example:

https://circleci.com/workflow-run/356aff13-2e2e-491e-86aa-e4dad56466a5

The “processes” job spent 18min on that step, but the “pages” one spent 1:30min for it. Config file is similar to both jobs, both use the same base Docker image. The “accountability” one is taking >25min and has not finished that step at the moment of writing this. Yesterday, this particular build took 45min on that same step:

https://circleci.com/gh/decidim/decidim/17820#build-timing

Is this a problem of my configuration? Did you get any other report for this problem? :confused:

Thanks!


#2

Update: the “accountability” job on https://circleci.com/workflow-run/356aff13-2e2e-491e-86aa-e4dad56466a5 was running for over 36minutes, stuck on the “Spin up project” step, before I canceled it. I rebuilt the workflow running only failed jobs:

https://circleci.com/gh/decidim/decidim/17859

The “Spin up env” step took only 0:37 minutes.

Any idea on why this is happening? Thanks!


#3

Seeing the same on a few of our (private) jobs too.


#4

+1 my builds are totally stuck at pulling large android ndk base image


#5

We see this problem too. We have had between 8 to 24 minutes in spin up today on deployment workflows.


#6

The problem seems to be with Dockerhub
https://status.docker.com/pages/incident/533c6539221ae15e3f000031/59f1da512cd214649ebc33b0


#7

Oh yes, pulling is faster now and the issue on Status Docker is marked as resolved.

Thanks for the feedback!


#8

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.