Gitlab runner didn't auto cancel a long running job

Problem to solve

Gitlab runner for one of my jobs ran for 110+ hours despite having the default 1 hour max job timeout set for runners. Now I have to buy my way out of these used minutes, unless there is another way? Shouldn’t the job have been automatically canceled by gitlab?

Here’s the details:
Duration: 6623 minutes 53 seconds

Finished: 1 week ago

Queued: 1 second

Timeout: 1h (from project)

Runner: #12270848 (ns46NMmJT) 2-green.saas-linux-small-amd64.runners-manager.gitlab.com/default

  • What are you seeing, and how does that differ from what you expect to see?
    I expect gitlab to cancel long running jobs.

Steps to reproduce

Create a long running job and see if gitlab stops the job after the default 1 hour timeout.