711619 - Please turn on every build and test that runs (visible) on mozilla-central for the fx-team tree

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Phil Ringnalda (:philor)]

Since Fx-Team is pretty much just another mozilla-inbound, rather than the "browser/-only" that the set of builds makes it look like we thought it would be, we need to have it run everything an integration branch needs to run, to avoid merging bustage like we did today.

Everything that's visible or about to be visible on mozilla-central is the goal, which I presume can be reached by just giving it everything that's on mozilla-inbound, including Android and periodic PGO, those being the most obviously missing things.

"<gavin>: no, the latter "turn everything on"" would be the owner's stamp of approval.

Comment 1

[Rob Campbell [:rc] (:robcee)]

ftr, as one of the owners (prefer "vikings") of fx-team, I approve of the intent of this bug.

Comment 2

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

found in triage: 

aiui, the ask here is to have the "fx-team" branch run the same builds/tests as are run on mozilla-inbound, so "fx-team" can be used as another integration branch.



(grabbing to investigate if I can do this during a lull over vacation. unclear why "critical", can you elaborate if I've missed some nuance of this bug)

Comment 3

[Phil Ringnalda (:philor)]

Fx-Team already is used as an integration branch, and has been as long as I can remember it having existed. Critical because right after we finally recovered from the Windows PGO *build* bustage, an Fx-Team merge landed both Android test bustage and Windows PGO test bustage.

Comment 4

[Rob Campbell [:rc] (:robcee)]

Not sure it's critical, but we should definitely mirror what's happening on central.

Comment 5

[Justin Dolske [:Dolske]]

Turn on all the things .o/

Comment 6

[:Gavin Sharp [email: [e-mail]]]

John: can you make this happen ASAP? fx-team continues to be used as an integration branch, and so this bug continues to cause problems for our merges.

Comment 7

[Phil Ringnalda (:philor)]

Attachment: probable configs

I sort of vaguely suspect this works. My theories:

* dropping the 'enabled_products': ['firefox'] gives us the default, ['firefox', 'mobile']

* adding pgo_strategy and pgo_platforms will give us periodic pgo, with the default 6 hours because I can't come up with a better strategy or interval

* the explicitly listed remote talos_suites must date back to before they were part of the default set (and then stayed around for unclear reasons partway through the bug, when it became possible to drop the mobile product), and are now just risking that it'll be weird and off-default if the default set changes

Comment 8

[Chris AtLee [:catlee]]

Comment on attachment 590627 [details] [diff] [review]
probable configs

looks good to me! thanks for grabbing this philor.

Comment 9

[Phil Ringnalda (:philor)]

Comment on attachment 590627 [details] [diff] [review]
probable configs

http://hg.mozilla.org/build/buildbot-configs/rev/e6670e401f91

Comment 10

[Armen [:armenzg]]

This is live on production as of 11:40 AM PDT.

Comment 11

[Phil Ringnalda (:philor)]

And both Android and PGO are up to their usual mischief there now :)