This explains all the flakiness of content_browsertests on that bot recently then.. 

https://build.chromium.org/p/chromium.android/builders/Lollipop%20Phone%20Tester?numbuilds=100

shard #0 timed out, took too much time to complete

Could the hard cap perhaps be increased while the cause of the increase is tracked down? content_browsertests failed 3 out of the past 7 builds on that bot - this seems unacceptably flaky..

I am typically reticent to bump timeouts, as people (myself included) are liable to let them stay in their elevated state,  but I suppose it's better than persistently flaking.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/fe235789d57f3c60dbf5dd45f0aaa82cea97a5e4

commit fe235789d57f3c60dbf5dd45f0aaa82cea97a5e4
Author: John Budorick <jbudorick@chromium.org>
Date: Wed Jun 07 19:46:05 2017

[android] Bump content_browsertests timeout on L Phone to 30min.

TBR=agrieve@chromium.org,awdf@chromium.org

Bug: 728387
Change-Id: Id366ab03c5bda2681544eebc8428edf098a991f1
Reviewed-on: https://chromium-review.googlesource.com/527233
Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Anita Woodruff <awdf@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#477732}
[modify] https://crrev.com/fe235789d57f3c60dbf5dd45f0aaa82cea97a5e4/testing/buildbot/chromium.android.json