B2G automation should use busybox during the install_gecko step if it's available

RESOLVED FIXED in Firefox 19

Status

Testing
General
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: ahal, Assigned: ahal)

Tracking

unspecified
mozilla21
ARM
Gonk (Firefox OS)
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox19 fixed, firefox20 fixed, firefox21 fixed, b2g18 fixed, b2g18-v1.0.0 wontfix, b2g18-v1.0.1 fixed)

Details

Attachments

(3 attachments)

The setup time is about 6-10 minutes. There are now 18 B2G emulator chunks across the various tests which equals almost 3 hours of slave time per push wasted on setup. Lets try and speed this up.

One quick win is to install busybox on the emulators and use that to copy all the gecko files over at once. I don't know how much faster it will be.
Assignee: nobody → ahalberstadt
Status: NEW → ASSIGNED
Depends on: 821865
Created attachment 697935 [details] [diff] [review]
Patch 1.0 - install with busybox

I'll push this to ash to test it out since it requires a mozharness change too.
Attachment #697935 - Flags: review?(jgriffin)
Created attachment 697945 [details] [diff] [review]
Patch 1.0 (mozharness) - pass in busybox
Attachment #697945 - Flags: review?(jgriffin)
Attachment #697935 - Flags: review?(jgriffin) → review+
Attachment #697945 - Flags: review?(jgriffin) → review+
Preliminary results seem to show that this cuts down 2-3 minutes per chunk. That's a bigger win than I was expecting.
I'll have to land the gecko patch everywhere before landing the mozharness one. I'll wait till next week when I'll be around all day to supervise it.
In order to make sure we don't get any failures I had to commit a part 1 gecko patch which is just the changes to add the busybox arg to the reftest and mochitest harnesses.

https://hg.mozilla.org/integration/mozilla-inbound/rev/7744b9769935
https://hg.mozilla.org/releases/mozilla-aurora/rev/f705a043ad9c
https://hg.mozilla.org/releases/mozilla-b2g18/rev/171baeed6231

Once this lands on central I'll commit the mozharness patch, then I can safely commit the marionette portion of the gecko patch.
Whiteboard: [leave-open]

Comment 7

5 years ago
Part 1 landed with an incorrect bug number (bug 812012). Happened to spot it by chance, but not until after the script had closed that bug. 

Ideally please can we have a backout + reland (n the same push, with DONTBUILD on the topmost changeset), so hg annotate shows the correct bug number?

https://hg.mozilla.org/mozilla-central/rev/7744b9769935

Comment 8

5 years ago
(Also note that part 1 missed the merge of mozilla20 to aurora; so needs to land there too)

Updated

5 years ago
status-b2g18: --- → fixed
status-firefox19: --- → fixed
status-firefox20: --- → affected
status-firefox21: --- → fixed
Target Milestone: --- → mozilla21
gecko patch part 2:
https://hg.mozilla.org/integration/mozilla-inbound/rev/999039502afb

I probably won't bother landing on aurora/b2g18 as it isn't something that's critical.
Whiteboard: [leave-open]
Crap. I just realized that the install_gecko step is happening before the install_busybox step. This means a third gecko patch is needed.
Created attachment 699347 [details] [diff] [review]
Patch 1.1 - install_busybox step needs to happen before install_gecko step
Attachment #699347 - Flags: review?(jgriffin)
Whiteboard: [leave-open]
Attachment #699347 - Flags: review?(jgriffin) → review+
https://hg.mozilla.org/mozilla-central/rev/999039502afb
https://hg.mozilla.org/mozilla-central/rev/564336aa34f6
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
https://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/d6d3e797d1ae
status-b2g18-v1.0.0: --- → wontfix
status-b2g18-v1.0.1: --- → fixed
You need to log in before you can comment on or make changes to this bug.