1452904 - Rebalance the Travis test chunks

Status: RESOLVED FIXED

(Tree Management :: Treeherder, enhancement, P1)

Description

[Ed Morley [:emorley]]

Now that we have the Selenium and Python 3 jobs, we have 7 jobs being run - which turns into 14 jobs for PRs where both PR and branch versions of the jobs are run.

This means that not all jobs start straight away (Travis presumably has some concurrency limit), plus with 14 jobs there's a greater chance at least one will hit an intermittent infrastructure issue.

The reason for the extreme chunking was to try and reduce the python unit test end to end times - however:
(a) setup time is now a significant chunk of the overall runtime (switching to Docker may help with this, if we can get `cache_from` working), so chunking gives diminishing returns
(b) the long pole is now the selenium job (which is less easy to chunk since it needs the time-consuming `yarn build`), so chunking the others doesn't really help

Comment 1

[GitHub Bugzilla PR Linker]

Attachment: Link to GitHub pull-request: https://github.com/mozilla/treeherder/pull/3424

Comment 2

[Treeherder GitHub Bugbot]

Commit pushed to master at https://github.com/mozilla/treeherder

https://github.com/mozilla/treeherder/commit/d789f62bf8f6cb2c6aa6ec5f16ec9a463dcded22
Bug 1452904 - Rebalance the Travis test chunks (#3424)

This merges the three separate non-selenium Python test jobs into
one, reducing the overall job count from 7 to 5. This helps avoid
hitting Travis concurrency limits, that delay starting the selenium
job (which is the long pole for the end to end time).