Attempt to split Travis job into 2

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
5 years ago
5 years ago

People

(Reporter: zcampbell, Assigned: zcampbell)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

46 bytes, text/x-github-pull-request
jlal
: feedback+
Details | Review | Splinter Review
(Assignee)

Description

5 years ago
Just trial this in a pull and see whether James/Gareth are happy with both the idea and technical solution.
(Assignee)

Comment 1

5 years ago
Created attachment 8366599 [details] [review]
github pr

Notes:
There is a higher-level solution which involves splitting the tests to run at manifest file level but that is more complex and I don't know of any timeframe for resolution by a-team.

This is a solution that we're using to reasonable effect on the device testing. It's in theory more difficult to maintain but in practice not much so and for that matter QA will take control of it.

The bulk of the time is still taken by the make steps but, given free Travis nodes, this will result in a shorter end-to-end test run.
Attachment #8366599 - Flags: feedback?(jlal)
Attachment #8366599 - Flags: feedback?(gaye)
(In reply to Zac C (:zac) from comment #1)
> There is a higher-level solution which involves splitting the tests to run
> at manifest file level but that is more complex and I don't know of any
> timeframe for resolution by a-team.

This has been discussed but I don't think there's a bug for it.
I would prefer for you all to abstract the parallelization into the test harness itself. I am willing to bet you can achieve close to the same level of parallelism across two threads on a single travis vm as you can by using two separate vms (perhaps even more?). What's more is that you'll also speed up builds locally and on TBPL if you make the improvements in the harness. Having test suites spread across multiple build steps will just confuse everyone more.
Attachment #8366599 - Flags: feedback?(gaye)
(Assignee)

Comment 4

5 years ago
Yes that would be even better but we'd need the help of the a-team to achieve that, I couldn't give a timeframe for something like that, certainly not even this quarter.
Comment on attachment 8366599 [details] [review]
github pr

Looks similar (but better) then the original hack I tried... I think this is an acceptable approach until we have both better CI and testing tools to help us with this problem.
Attachment #8366599 - Flags: feedback?(jlal) → feedback+
(Assignee)

Comment 6

5 years ago
We're managing the build times OK now that the Wait changed saved a lot of time.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.