Run Chrome EarlGrey tests on FYI.

Run Chrome EarlGrey tests on FYI.

Now that Chrome can be built upstream, we should run integration
tests.

BUG=675788
Committed: https://crrev.com/6c5381ffdf7c3b8efc3bb9b190bbb10d1d7f003d
Cr-Commit-Position: refs/heads/master@{#439668}

[baxley, 2016-12-20 00:37:03]

baxley@chromium.org changed reviewers:
+ rohitrao@chromium.org, sdefresne@chromium.org

[rohitrao (ping after 24h), 2016-12-20 00:49:26]

lgtm

FYI means we can make changes aggressively.  Let's turn these on and see how
they do?

[rohitrao (ping after 24h), 2016-12-20 00:50:03]

rohitrao@chromium.org changed reviewers:
+ smut@google.com

[rohitrao (ping after 24h), 2016-12-20 00:50:03]

Only thing we have to watch for is capacity.  +smut because we'll be adding
additional load to the swarming bots.

[smut, 2016-12-20 00:52:52]

On 2016/12/20 00:50:03, rohitrao wrote:
> Only thing we have to watch for is capacity.  +smut because we'll be adding
> additional load to the swarming bots.

lgtm let's see what hit capacity takes. I suspect we need more because a lot
more stuff has been added lately.

[sdefresne, 2016-12-20 00:53:25]

sdefresne@chromium.org changed reviewers:
+ olivierrobin@chromium.org

[sdefresne, 2016-12-20 00:53:25]

lgtm

https://codereview.chromium.org/2588193002/diff/20001/ios/build/bots/chromium...
File ios/build/bots/chromium.fyi/EarlGreyiOS.json (right):

https://codereview.chromium.org/2588193002/diff/20001/ios/build/bots/chromium...
ios/build/bots/chromium.fyi/EarlGreyiOS.json:27: "app":
"ios_chrome_reading_list_egtests",
I think this test need some additional "args", doesn't it? We should ask
+olivierrobin whether this is now working without "args" or not.

[smut, 2016-12-20 00:54:16]

On 2016/12/20 00:52:52, smut wrote:
> On 2016/12/20 00:50:03, rohitrao wrote:
> > Only thing we have to watch for is capacity.  +smut because we'll be adding
> > additional load to the swarming bots.
> 
> lgtm let's see what hit capacity takes. I suspect we need more because a lot
> more stuff has been added lately.

Oh this is upstream. I'm less concerned since we got a lot of capacity recently.

[rohitrao (ping after 24h), 2016-12-20 00:54:27]

https://codereview.chromium.org/2588193002/diff/20001/ios/build/bots/chromium...
File ios/build/bots/chromium.fyi/EarlGreyiOS.json (right):

https://codereview.chromium.org/2588193002/diff/20001/ios/build/bots/chromium...
ios/build/bots/chromium.fyi/EarlGreyiOS.json:27: "app":
"ios_chrome_reading_list_egtests",
On 2016/12/20 00:53:25, sdefresne wrote:
> I think this test need some additional "args", doesn't it? We should ask
> +olivierrobin whether this is now working without "args" or not.

Let's either match what we did downstream or remove it for now?

[baxley, 2016-12-20 00:56:38]

Removed the reading list suite. Thanks for the reviews!

https://codereview.chromium.org/2588193002/diff/20001/ios/build/bots/chromium...
File ios/build/bots/chromium.fyi/EarlGreyiOS.json (right):

https://codereview.chromium.org/2588193002/diff/20001/ios/build/bots/chromium...
ios/build/bots/chromium.fyi/EarlGreyiOS.json:27: "app":
"ios_chrome_reading_list_egtests",
On 2016/12/20 00:54:27, rohitrao wrote:
> On 2016/12/20 00:53:25, sdefresne wrote:
> > I think this test need some additional "args", doesn't it? We should ask
> > +olivierrobin whether this is now working without "args" or not.
> 
> Let's either match what we did downstream or remove it for now?

Yup. Removed.

[baxley, 2016-12-20 00:56:42]

The CQ bit was checked by baxley@chromium.org

[baxley, 2016-12-20 00:56:42]

The patchset sent to the CQ was uploaded after l-g-t-m from
rohitrao@chromium.org, smut@google.com, sdefresne@chromium.org
Link to the patchset: https://codereview.chromium.org/2588193002/#ps40001
(title: "remove reading list")

[commit-bot: I haz the power, 2016-12-20 00:56:59]

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-12-20 02:12:18]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1482195402476320,
"parent_rev": "3649039e8052104f429d25073f5089ec466206ba", "commit_rev":
"b72ea9c624195448c0b851aa1cbf582085ac0a26"}

[commit-bot: I haz the power, 2016-12-20 02:12:49]

Description was changed from

==========
Run Chrome EarlGrey tests on FYI.

Now that Chrome can be built upstream, we should run integration
tests.

BUG=675788
==========

to

==========
Run Chrome EarlGrey tests on FYI.

Now that Chrome can be built upstream, we should run integration
tests.

BUG=675788

Review-Url: https://codereview.chromium.org/2588193002
==========

[commit-bot: I haz the power, 2016-12-20 02:12:50]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-12-20 02:15:32]

Description was changed from

==========
Run Chrome EarlGrey tests on FYI.

Now that Chrome can be built upstream, we should run integration
tests.

BUG=675788

Review-Url: https://codereview.chromium.org/2588193002
==========

to

==========
Run Chrome EarlGrey tests on FYI.

Now that Chrome can be built upstream, we should run integration
tests.

BUG=675788

Committed: https://crrev.com/6c5381ffdf7c3b8efc3bb9b190bbb10d1d7f003d
Cr-Commit-Position: refs/heads/master@{#439668}
==========

[commit-bot: I haz the power, 2016-12-20 02:15:33]

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