[build/android] Increase timeout of perf tests to 3 hours

[build/android] Increase timeout of perf tests to 3 hours

Some tests are now timing out because they take longer to run.

BUG=655965, 655648
Committed: https://crrev.com/c7f66928a50ec3a5751c245764f9872b7c494262
Cr-Commit-Position: refs/heads/master@{#425483}

[perezju, 2016-10-14 12:54:01]

perezju@chromium.org changed reviewers:
+ rnephew@chromium.org

[rnephew (Reviews Here), 2016-10-14 16:48:57]

On 2016/10/14 12:54:02, perezju wrote:

lgtm

[rnephew (Reviews Here), 2016-10-14 21:08:31]

The CQ bit was checked by rnephew@chromium.org

[commit-bot: I haz the power, 2016-10-14 21:09:19]

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-10-14 21:59:43]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-10-14 22:01:39]

Description was changed from

==========
[build/android] Increase timeout of perf tests to 3 hours

Some tests are now timing out because they take longer to run.

BUG=655965,655648
==========

to

==========
[build/android] Increase timeout of perf tests to 3 hours

Some tests are now timing out because they take longer to run.

BUG=655965,655648

Committed: https://crrev.com/c7f66928a50ec3a5751c245764f9872b7c494262
Cr-Commit-Position: refs/heads/master@{#425483}
==========

[commit-bot: I haz the power, 2016-10-14 22:01:40]

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

[jbudorick, 2016-10-18 17:29:24]

On 2016/10/14 22:01:40, commit-bot: I haz the power wrote:
> Patchset 1 (id:??) landed as
> https://crrev.com/c7f66928a50ec3a5751c245764f9872b7c494262
> Cr-Commit-Position: refs/heads/master@{#425483}

What tests are taking longer than an hour when running correctly?

[rnephew (Reviews Here), 2016-10-18 17:30:22]

On 2016/10/18 17:29:24, jbudorick wrote:
> On 2016/10/14 22:01:40, commit-bot: I haz the power wrote:
> > Patchset 1 (id:??) landed as
> > https://crrev.com/c7f66928a50ec3a5751c245764f9872b7c494262
> > Cr-Commit-Position: refs/heads/master@{#425483}
> 
> What tests are taking longer than an hour when running correctly?

The system health ones now run with pageset-repeat=3 which pushes them over an
hour.

[rnephew (Reviews Here), 2016-10-18 17:35:10]

On 2016/10/18 17:30:22, rnephew (Reviews Here) wrote:
> On 2016/10/18 17:29:24, jbudorick wrote:
> > On 2016/10/14 22:01:40, commit-bot: I haz the power wrote:
> > > Patchset 1 (id:??) landed as
> > > https://crrev.com/c7f66928a50ec3a5751c245764f9872b7c494262
> > > Cr-Commit-Position: refs/heads/master@{#425483}
> > 
> > What tests are taking longer than an hour when running correctly?
> 
> The system health ones now run with pageset-repeat=3 which pushes them over an
> hour.

To give a specific example:
I 9855.147s device_shard_helper(0)  system_health.memory_mobile : exit_code=5 in
8297 secs on device 03848d7af0e9447d 

https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_Ne...

[perezju, 2016-10-19 10:48:21]

On 2016/10/18 17:29:24, jbudorick wrote:
> On 2016/10/14 22:01:40, commit-bot: I haz the power wrote:
> > Patchset 1 (id:??) landed as
> > https://crrev.com/c7f66928a50ec3a5751c245764f9872b7c494262
> > Cr-Commit-Position: refs/heads/master@{#425483}
> 
> What tests are taking longer than an hour when running correctly?

TL;DR: system health and loading.mobile.

More context in the attached bugs.