Runner fails due to timeout exceeded (Cloning repository...)
Summary
After release of 10.0 runner on free private projects, I'm getting such error:
Runners starts then freezes in Cloning Repository
state.
Steps to reproduce
Run any pipeline manually or by push event.
Actual behavior
Runner fails after timeout time exceeded.
Expected behavior
Runner should process as usual.
Relevant logs and/or screenshots
Running with gitlab-runner 10.0.0-rc.1 (6331f360)
on docker-auto-scale (e11ae361)
Using Docker executor with image docker:git ...
Starting service docker:dind ...
Pulling docker image docker:dind ...
Using docker image docker:dind ID=sha256:b9145b364a203c0afc538ca615b3470e41729edfb7338017f5d4eeb5b13b2d90 for docker service...
Waiting for services to be up and running...
Using docker image sha256:83709b5d2e611817625ee2eb1b7d0758cfefb5da36512159783848c5adcc7b42 for predefined container...
Pulling docker image docker:git ...
Using docker image docker:git ID=sha256:5917639be9495ab183f357e8bafafea82449f0c4b12b745eef8bd23d474220ca for build container...
Running on runner-e11ae361-project-2116805-concurrent-0 via runner-e11ae361-machine-1506609038-c5a81c25-digital-ocean-2gb...
Cloning repository...
Cloning into '/builds/xxx/yyy'...
ERROR: Job failed: execution took longer than 1h30m0s seconds
Environment description
GitLab.com Runners (10.0.0-rc.1)
Used GitLab Runner version
10.0.0-rc.1