Adding new pool with dedicated nexus4 device

Adding new pool with dedicated nexus4 device

For Findit to trigger test try jobs correctly against WebKit Android (Nexus4), a bot with a dedicated device is needed. Without it test tryjobs will fail due to device_status_check exceptions. This change points the variable builder to a pool with a dedicated slave with device.

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

[lijeffrey, 2016-04-22 19:24:16]

Description was changed from

==========
Adding new pool with dedicated nexus4 device

BUG=
==========

to

==========
Adding new pool with dedicated nexus4 device

For Findit to trigger test try jobs correctly against WebKit Android (Nexus4), a
bot with a dedicated device is needed. Without it test tryjobs will fail due to
device_status_check exceptions. This change points the variable builder to a
pool with a dedicated slave with device.

BUG=606007
==========

[lijeffrey, 2016-04-22 19:24:16]

lijeffrey@chromium.org changed reviewers:
+ bpastene@chromium.org, iannucci@chromium.org, sergeyberezin@chromium.org

[lijeffrey, 2016-04-22 19:25:19]

Hey Ben,

Thanks for helping get that slave with a nexus 4 set up. Can you please review
this change to get Findit's variable builder pointing to a newly added pool with
that slave/device?

Thanks,
Jeff

[Sergey Berezin, 2016-04-22 21:13:58]

LGTM for code; I didn't check that the slave name is correct. Is there a bug
where the slave was provisioned, for reference?

[lijeffrey, 2016-04-22 21:19:16]

On 2016/04/22 21:13:58, Sergey Berezin wrote:
> LGTM for code; I didn't check that the slave name is correct. Is there a bug
> where the slave was provisioned, for reference?

Oh sorry forgot to add that,
https://bugs.chromium.org/p/chromium/issues/detail?id=604047 was to get us a
public bot with a device, does everything check out?

[bpastene, 2016-04-22 21:31:35]

On 2016/04/22 21:13:58, Sergey Berezin wrote:
> LGTM for code; I didn't check that the slave name is correct. Is there a bug
> where the slave was provisioned, for reference?

Yep, the bot's correct and free for use.

lgtm

[Sergey Berezin, 2016-04-22 21:33:08]

On 2016/04/22 21:19:16, lijeffrey wrote:
> On 2016/04/22 21:13:58, Sergey Berezin wrote:
> > LGTM for code; I didn't check that the slave name is correct. Is there a bug
> > where the slave was provisioned, for reference?
> 
> Oh sorry forgot to add that,
> https://bugs.chromium.org/p/chromium/issues/detail?id=604047 was to get us a
> public bot with a device, does everything check out?

Thanks, lgtm! Good to go.

[lijeffrey, 2016-04-22 23:45:33]

The CQ bit was checked by lijeffrey@chromium.org

[commit-bot: I haz the power, 2016-04-22 23:45:43]

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

[commit-bot: I haz the power, 2016-04-22 23:51:21]

Description was changed from

==========
Adding new pool with dedicated nexus4 device

For Findit to trigger test try jobs correctly against WebKit Android (Nexus4), a
bot with a dedicated device is needed. Without it test tryjobs will fail due to
device_status_check exceptions. This change points the variable builder to a
pool with a dedicated slave with device.

BUG=606007
==========

to

==========
Adding new pool with dedicated nexus4 device

For Findit to trigger test try jobs correctly against WebKit Android (Nexus4), a
bot with a dedicated device is needed. Without it test tryjobs will fail due to
device_status_check exceptions. This change points the variable builder to a
pool with a dedicated slave with device.

BUG=606007

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

[commit-bot: I haz the power, 2016-04-22 23:51:22]

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