[Android] Add mb_config entries for chromium.linux and tryserver.chromium.android.

[Android] Add mb_config entries for chromium.linux and tryserver.chromium.android.

BUG=576993
Committed: https://crrev.com/3d1c635702ae21b79e0d86f38c2b6d02ede96cb0
Cr-Commit-Position: refs/heads/master@{#380056}

[jbudorick, 2016-03-08 18:48:33]

jbudorick@chromium.org changed reviewers:
+ dpranke@chromium.org

[Dirk Pranke, 2016-03-08 23:01:30]

lgtm

https://codereview.chromium.org/1774233002/diff/1/tools/mb/mb_config.pyl
File tools/mb/mb_config.pyl (right):

https://codereview.chromium.org/1774233002/diff/1/tools/mb/mb_config.pyl#newc...
tools/mb/mb_config.pyl:547: 'Linux Tests (dbg)(1)(32)': 'none',
At one point in time these were intentionally un-sorted. Instead they were
listed in the order that they appear on /builders on the buildbot waterfall. My
thinking was that it made it slightly easier to manually scan the list to make
sure we had every builder.

In retrospect it's probably lower maintenance to sort the lists like you've done
and check that they match other ways (ideally programmatically).

[jbudorick, 2016-03-08 23:46:04]

https://codereview.chromium.org/1774233002/diff/1/tools/mb/mb_config.pyl
File tools/mb/mb_config.pyl (right):

https://codereview.chromium.org/1774233002/diff/1/tools/mb/mb_config.pyl#newc...
tools/mb/mb_config.pyl:547: 'Linux Tests (dbg)(1)(32)': 'none',
On 2016/03/08 23:01:30, Dirk Pranke wrote:
> At one point in time these were intentionally un-sorted. Instead they were
> listed in the order that they appear on /builders on the buildbot waterfall.
My
> thinking was that it made it slightly easier to manually scan the list to make
> sure we had every builder.
> 
> In retrospect it's probably lower maintenance to sort the lists like you've
done
> and check that they match other ways (ideally programmatically).

Alphabetically makes it easier to check for any one builder. I can see how
bot-order would make it easier to scan for entire sections of the waterfall,
though.

Any thoughts about how would we go about enforcing these lists programmatically
short of somehow comparing them against the relevant master.cfg?

[Dirk Pranke, 2016-03-09 00:19:10]

On 2016/03/08 23:46:04, jbudorick wrote:
> Alphabetically makes it easier to check for any one builder. I can see how
> bot-order would make it easier to scan for entire sections of the waterfall,
> though.

Ayup.

> Any thoughts about how would we go about enforcing these lists
programmatically
> short of somehow comparing them against the relevant master.cfg?

It would be easy to query the masters via JSON and get the list of builders that
way and compare
against the keys in the dict. I just haven't gotten around to it.

[jbudorick, 2016-03-09 00:21:09]

The CQ bit was checked by jbudorick@chromium.org

[commit-bot: I haz the power, 2016-03-09 00:21:42]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1774233002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1774233002/1

[commit-bot: I haz the power, 2016-03-09 03:52:23]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-03-09 03:53:44]

Description was changed from

==========
[Android] Add mb_config entries for chromium.linux and
tryserver.chromium.android.

BUG=576993
==========

to

==========
[Android] Add mb_config entries for chromium.linux and
tryserver.chromium.android.

BUG=576993

Committed: https://crrev.com/3d1c635702ae21b79e0d86f38c2b6d02ede96cb0
Cr-Commit-Position: refs/heads/master@{#380056}
==========

[commit-bot: I haz the power, 2016-03-09 03:53:45]

Patchset 1 (id:??) landed as
https://crrev.com/3d1c635702ae21b79e0d86f38c2b6d02ede96cb0
Cr-Commit-Position: refs/heads/master@{#380056}