Job timeout neglected
Summary
Recently, one of my CI jobs ran for more than 2000 minutes although in the repository's CI settings a job timeout of 60 minutes is set. Below is the job's output. Apparently it got stuck while downloading a Docker image.
Running with gitlab-runner 10.2.0-rc.1 (927894e6) on docker-auto-scale (e11ae361)
Using Docker executor with image alpine ...
Starting service postgres:latest ...
Pulling docker image postgres:latest ...
Steps to reproduce
I don't really now and can't run the job again because I have no free minutes anymore.
What is the current bug behavior?
No cancellation despite running for longer than the defined in job timeout. In fact, it ran for about 1 and a half days (1 day 15:56:38).
What is the expected correct behavior?
The build should be canceled after x
minutes. Where x
is the amount of minutes defined in the job timeout settings.
Relevant logs and/or screenshots
Output of checks
This bug happens on GitLab.com