Default `timeout` not taken into account in `gitlab-ci.yml`

Summary

Setting "default timeout" in gitlab-ci.yml does not propagate to jobs in a setup with depends.

Steps to reproduce

According to the documentation, I should be able to declare a default timeout for all jobs in the gitlab-ci.yml:

default:
  timeout: 30 seconds

The gitlab-ci.yml is parsed correctly, but the jobs are not affected by this setting (they get my default project setting of 1 hour.)

However, when I set an individual job timeout, timeout: 5 minutes, it is correctly taken into account.

Note: I am wondering if it's related to the fact that I'm using different jobs as dependencies of each other through this interface:

job2:
  needs: [job1]

Example Project

I cannot share my project as an example, but this should be reproducible on any project with gitlab runners.

What is the current bug behavior?

Default timeout does not propagate to job.

What is the expected correct behavior?

All jobs should have the default timeout.

Relevant logs and/or screenshots

See above

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes