Move Mojo bots to chromium_fyi; remove mojo master.

Move Mojo bots to chromium_fyi; remove mojo master.

Remove unused chromium_mojo "Chromium Mojo Android".
Move chromium_mojo "Chromium Mojo Windows" to chromium_fyi "Mojo Windows".
Move chromium_mojo "Chromium Mojo Linux" to chromium_fyi "Mojo ChromiumOS".
(we now need fyi build/test coverage on chrome os, not desktop linux)

Move required slave configs; remove chromium_mojo master references.
Run "scripts/slave/unittests/recipe_simulation_test.py train"

This CL will be accompanied by: https://codereview.chromium.org/2114453002

BUG=619128
TEST=Chromium Mojo bots move to Chromium FYI master.
R=dpranke@chromium.org

Committed: https://chromium.googlesource.com/chromium/tools/build/+/71d600393f83c9b4ba693edbf61e79097db9a471

[msw, 2016-06-29 23:08:34]

Description was changed from

==========
Move Mojo bots to chromium_fyi; remove mojo master.

BUG=619128
==========

to

==========
Move Mojo bots to chromium_fyi; remove mojo master.

Remove unused chromium_mojo "Chromium Mojo Android".
Move chromium_mojo "Chromium Mojo Windows" to chromium_fyi "Mojo Windows".
Move chromium_mojo "Chromium Mojo Linux" to chromium_fyi "Mojo ChromiumOS".
(we now need fyi build/test coverage on chrome os, not desktop linux)

Move required slave configs; remove chromium_mojo master references.
Run "scripts/slave/unittests/recipe_simulation_test.py train"

This CL will be followed by: https://codereview.chromium.org/2114453002

BUG=619128
TEST=Chromium Mojo bots move to Chromium FYI master.
R=dpranke@chromium.org
==========

[msw, 2016-06-29 23:08:35]

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

[msw, 2016-06-29 23:14:59]

Hey Dirk, please take a careful look; thanks!
(Am I doing this right? Can I just land this before the testing/buildbot/*
changes, or should I do a two part copy then remove? Will I just need an fyi
master restart? Anything else?)

https://codereview.chromium.org/2112743002/diff/20001/scripts/slave/recipe_mo...
File scripts/slave/recipe_modules/chromium_tests/chromium_fyi.py (right):

https://codereview.chromium.org/2112743002/diff/20001/scripts/slave/recipe_mo...
scripts/slave/recipe_modules/chromium_tests/chromium_fyi.py:2288: 'Mojo
ChromiumOS': {
q: should these also specify either of these?
 'use_isolate': True,
 'enable_swarming': True,

[Dirk Pranke, 2016-06-29 23:23:49]

On 2016/06/29 23:14:59, msw wrote:
> Hey Dirk, please take a careful look; thanks!
> (Am I doing this right? Can I just land this before the testing/buildbot/*
> changes, or should I do a two part copy then remove? Will I just need an fyi
> master restart? Anything else?)

I would actually land the //testing/buildbot changes first, but it's pretty much
impossible
to land this sort of CL w/o breaking some builders temporarily, and since these
are FYI
builders either way, I don't think it matters too much.

You will need the fyi master restarted.

lgtm otherwise w/ nit addressed.

[msw, 2016-06-30 00:03:16]

On 2016/06/29 23:23:49, Dirk Pranke wrote:
> w/ nit addressed.

I don't see a nit, did you forget to publish?

[msw, 2016-06-30 00:04:33]

Description was changed from

==========
Move Mojo bots to chromium_fyi; remove mojo master.

Remove unused chromium_mojo "Chromium Mojo Android".
Move chromium_mojo "Chromium Mojo Windows" to chromium_fyi "Mojo Windows".
Move chromium_mojo "Chromium Mojo Linux" to chromium_fyi "Mojo ChromiumOS".
(we now need fyi build/test coverage on chrome os, not desktop linux)

Move required slave configs; remove chromium_mojo master references.
Run "scripts/slave/unittests/recipe_simulation_test.py train"

This CL will be followed by: https://codereview.chromium.org/2114453002

BUG=619128
TEST=Chromium Mojo bots move to Chromium FYI master.
R=dpranke@chromium.org
==========

to

==========
Move Mojo bots to chromium_fyi; remove mojo master.

Remove unused chromium_mojo "Chromium Mojo Android".
Move chromium_mojo "Chromium Mojo Windows" to chromium_fyi "Mojo Windows".
Move chromium_mojo "Chromium Mojo Linux" to chromium_fyi "Mojo ChromiumOS".
(we now need fyi build/test coverage on chrome os, not desktop linux)

Move required slave configs; remove chromium_mojo master references.
Run "scripts/slave/unittests/recipe_simulation_test.py train"

This CL will be accompanied by: https://codereview.chromium.org/2114453002

BUG=619128
TEST=Chromium Mojo bots move to Chromium FYI master.
R=dpranke@chromium.org
==========

[Dirk Pranke, 2016-06-30 00:12:04]

Odd, I don't know why that didn't get published before ...

https://codereview.chromium.org/2112743002/diff/20001/scripts/slave/recipe_mo...
File scripts/slave/recipe_modules/chromium_tests/chromium_fyi.py (right):

https://codereview.chromium.org/2112743002/diff/20001/scripts/slave/recipe_mo...
scripts/slave/recipe_modules/chromium_tests/chromium_fyi.py:2288: 'Mojo
ChromiumOS': {
On 2016/06/29 23:14:59, msw wrote:
> q: should these also specify either of these?
>  'use_isolate': True,
>  'enable_swarming': True,

Probably. We shouldn't be deploying machines that run tests that aren't using
swarming at this point, but I don't believe those are the defaults.

[msw, 2016-06-30 01:43:35]

The CQ bit was checked by msw@chromium.org

[msw, 2016-06-30 01:43:35]

The patchset sent to the CQ was uploaded after l-g-t-m from dpranke@chromium.org
Link to the patchset: https://codereview.chromium.org/2112743002/#ps40001
(title: "Add 'use_isolate': True and 'enable_swarming': True.")

[commit-bot: I haz the power, 2016-06-30 01:43:42]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[msw, 2016-06-30 01:43:53]

The CQ bit was unchecked by msw@chromium.org

[msw, 2016-06-30 01:45:32]

https://codereview.chromium.org/2112743002/diff/20001/scripts/slave/recipe_mo...
File scripts/slave/recipe_modules/chromium_tests/chromium_fyi.py (right):

https://codereview.chromium.org/2112743002/diff/20001/scripts/slave/recipe_mo...
scripts/slave/recipe_modules/chromium_tests/chromium_fyi.py:2288: 'Mojo
ChromiumOS': {
On 2016/06/30 00:12:04, Dirk Pranke wrote:
> On 2016/06/29 23:14:59, msw wrote:
> > q: should these also specify either of these?
> >  'use_isolate': True,
> >  'enable_swarming': True,
> 
> Probably. We shouldn't be deploying machines that run tests that aren't using
> swarming at this point, but I don't believe those are the defaults.

Done.

[msw, 2016-06-30 03:06:35]

The CQ bit was checked by msw@chromium.org

[commit-bot: I haz the power, 2016-06-30 03:06:45]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-06-30 03:11:25]

Description was changed from

==========
Move Mojo bots to chromium_fyi; remove mojo master.

Remove unused chromium_mojo "Chromium Mojo Android".
Move chromium_mojo "Chromium Mojo Windows" to chromium_fyi "Mojo Windows".
Move chromium_mojo "Chromium Mojo Linux" to chromium_fyi "Mojo ChromiumOS".
(we now need fyi build/test coverage on chrome os, not desktop linux)

Move required slave configs; remove chromium_mojo master references.
Run "scripts/slave/unittests/recipe_simulation_test.py train"

This CL will be accompanied by: https://codereview.chromium.org/2114453002

BUG=619128
TEST=Chromium Mojo bots move to Chromium FYI master.
R=dpranke@chromium.org
==========

to

==========
Move Mojo bots to chromium_fyi; remove mojo master.

Remove unused chromium_mojo "Chromium Mojo Android".
Move chromium_mojo "Chromium Mojo Windows" to chromium_fyi "Mojo Windows".
Move chromium_mojo "Chromium Mojo Linux" to chromium_fyi "Mojo ChromiumOS".
(we now need fyi build/test coverage on chrome os, not desktop linux)

Move required slave configs; remove chromium_mojo master references.
Run "scripts/slave/unittests/recipe_simulation_test.py train"

This CL will be accompanied by: https://codereview.chromium.org/2114453002

BUG=619128
TEST=Chromium Mojo bots move to Chromium FYI master.
R=dpranke@chromium.org

Committed:
https://chromium.googlesource.com/chromium/tools/build/+/71d600393f83c9b4ba69...
==========

[commit-bot: I haz the power, 2016-06-30 03:11:26]

Committed patchset #3 (id:40001) as
https://chromium.googlesource.com/chromium/tools/build/+/71d600393f83c9b4ba69...