Move Android Nexus 9 GPU bot to chromium.gpu.fyi waterfall.

Move Android Nexus 9 GPU bot to chromium.gpu.fyi waterfall.

This will be the first bot converted to the Chromium recipe. While
this transition is in progress, and especially since there is no
tryserver coverage for it, move it from the chromium.gpu waterfall
(which is sheriffed) to the chromium.gpu.fyi waterfall.

BUG=490984
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=300029

[Ken Russell (switch to Gerrit), 2016-04-19 23:43:36]

kbr@chromium.org changed reviewers:
+ bpastene@chromium.org, iannucci@chromium.org

[Ken Russell (switch to Gerrit), 2016-04-19 23:43:37]

bpastene or iannucci: PTAL

I note that scripts/slave/recipes/chromium.gpu.recipe_autogen.py knows that the
Android Debug (Nexus 9) bot is on the chromium.gpu waterfall, but I suspect that
execution of the autogenerated recipe doesn't care about which waterfall the bot
is actually on.

I'd just like to get the bot to do one build on the chromium.gpu.fyi waterfall
with its existing script setup before switching it to run the Chromium recipe
(which will initially stop running all of the tests).

[bpastene, 2016-04-19 23:52:53]

lgtm

On 2016/04/19 23:43:37, Ken Russell wrote:
> I note that scripts/slave/recipes/chromium.gpu.recipe_autogen.py knows that
the
> Android Debug (Nexus 9) bot is on the chromium.gpu waterfall, but I suspect
that
> execution of the autogenerated recipe doesn't care about which waterfall the
bot
> is actually on.

Yeah, it looks like it only cares about the name of the builder, and since
that's the same it _should_ work.

[aneeshm, 2016-04-19 23:58:32]

On 2016/04/19 23:43:37, Ken Russell wrote:
> bpastene or iannucci: PTAL
> 
> I note that scripts/slave/recipes/chromium.gpu.recipe_autogen.py knows that
the
> Android Debug (Nexus 9) bot is on the chromium.gpu waterfall, but I suspect
that
> execution of the autogenerated recipe doesn't care about which waterfall the
bot
> is actually on.
> 
> I'd just like to get the bot to do one build on the chromium.gpu.fyi waterfall
> with its existing script setup before switching it to run the Chromium recipe
> (which will initially stop running all of the tests).

That's right; the recipe doesn't care which waterfall it's being run on *as long
as the builder name is identical*.

For consistency and completeness, I'd suggest also changing the mastername=
property in the recipe's test case for this builder.

[Ken Russell (switch to Gerrit), 2016-04-20 00:55:02]

On 2016/04/19 23:58:32, aneeshm wrote:
> On 2016/04/19 23:43:37, Ken Russell wrote:
> > bpastene or iannucci: PTAL
> > 
> > I note that scripts/slave/recipes/chromium.gpu.recipe_autogen.py knows that
> the
> > Android Debug (Nexus 9) bot is on the chromium.gpu waterfall, but I suspect
> that
> > execution of the autogenerated recipe doesn't care about which waterfall the
> bot
> > is actually on.
> > 
> > I'd just like to get the bot to do one build on the chromium.gpu.fyi
waterfall
> > with its existing script setup before switching it to run the Chromium
recipe
> > (which will initially stop running all of the tests).
> 
> That's right; the recipe doesn't care which waterfall it's being run on *as
long
> as the builder name is identical*.
> 
> For consistency and completeness, I'd suggest also changing the mastername=
> property in the recipe's test case for this builder.

Done. CQ'ing.

[Ken Russell (switch to Gerrit), 2016-04-20 00:55:06]

The CQ bit was checked by kbr@chromium.org

[Ken Russell (switch to Gerrit), 2016-04-20 00:55:07]

The patchset sent to the CQ was uploaded after l-g-t-m from
bpastene@chromium.org
Link to the patchset: https://codereview.chromium.org/1901883004/#ps20001
(title: "Updated simulation test for N9 bot.")

[commit-bot: I haz the power, 2016-04-20 00:55:11]

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

[commit-bot: I haz the power, 2016-04-20 01:03:12]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-04-20 01:03:12]

Try jobs failed on following builders:
  Build Presubmit on tryserver.infra (JOB_FAILED,
https://build.chromium.org/p/tryserver.infra/builders/Build%20Presubmit/build...)

[Ken Russell (switch to Gerrit), 2016-04-20 01:06:29]

The CQ bit was checked by kbr@chromium.org

[Ken Russell (switch to Gerrit), 2016-04-20 01:06:30]

The patchset sent to the CQ was uploaded after l-g-t-m from
bpastene@chromium.org
Link to the patchset: https://codereview.chromium.org/1901883004/#ps40001
(title: "Fixed master specification for N9 bot.")

[commit-bot: I haz the power, 2016-04-20 01:06:32]

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

[commit-bot: I haz the power, 2016-04-20 01:10:49]

Description was changed from

==========
Move Android Nexus 9 GPU bot to chromium.gpu.fyi waterfall.

This will be the first bot converted to the Chromium recipe. While
this transition is in progress, and especially since there is no
tryserver coverage for it, move it from the chromium.gpu waterfall
(which is sheriffed) to the chromium.gpu.fyi waterfall.

BUG=490984
==========

to

==========
Move Android Nexus 9 GPU bot to chromium.gpu.fyi waterfall.

This will be the first bot converted to the Chromium recipe. While
this transition is in progress, and especially since there is no
tryserver coverage for it, move it from the chromium.gpu waterfall
(which is sheriffed) to the chromium.gpu.fyi waterfall.

BUG=490984

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=300029
==========

[commit-bot: I haz the power, 2016-04-20 01:10:50]

Committed patchset #3 (id:40001) as
http://src.chromium.org/viewvc/chrome?view=rev&revision=300029