764252 - Android tests are permaorange on mozilla-release

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Phil Ringnalda (:philor)]

Attachment: fix

+++ This bug was initially created as a clone of Bug #734704 +++

+++ This bug was initially created as a clone of Bug #725193 +++

See: https://tbpl.mozilla.org/?tree=Mozilla-Release&noignore=1


A) We should make changing the branding for on-push builds part of the merge, rather than something that I decide to file, or to not file and instead hide the tests, based on the current tenant of mozilla-release.

B) There will come a day, probably a Thursday like July 12th or maybe August 23rd, when we will want to have Android tests work on mozilla-release. Right now, we have no idea whether they will, since the last time they were not broken by branding was April 2nd. Despite having no interest in the test _results_ of mozilla-release13, we should swap the branding just to see that the buildbot bits still work on m-r.

Comment 1

[Alex Keybl [:akeybl]]

The patch looks good to me, but I think Aki may need to r+ as lsblakk is currently out of town and I'm not a peer on this module.

Lukas will add the necessary instructions (for XF and FN) to https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Configuration once she's back.

Comment 2

[Phil Ringnalda (:philor)]

https://hg.mozilla.org/releases/mozilla-release/rev/085ec2f71ec6

https://tbpl.mozilla.org/?tree=Mozilla-Release&noignore=1&rev=085ec2f71ec6&jobname=android looks, alas, quite normal - the annotations to green up R2 and R3 come down on the next merge, as does a talos.zip that knows how to run rck2 and rpr, and a buildbot reconfig that turns on rck (which should be turning on rck2 and rpr, which should be off, but it's not worth the trouble to turn them off for just a few more weeks).