📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12ac3e55640000

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/12ac3e55640000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/10fa7165640000

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/10fa7165640000

All of the runs failed. The most common error (20/20 runs) was:
TimeoutException: 

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/16ce5f6d640000

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/16ce5f6d640000

All of the runs failed. The most common error (19/20 runs) was:
TimeoutException: 

 Issue 878252  has been merged into this issue.

Bisect fails to reproduce. So I think something is really strange here. Juan: can you take a look?

Strange ... I'll start by disabling the failing stories.

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

commit de0853f4ff4ca1438053999950702154117947b2
Author: Juan Antonio Navarro Perez <perezju@chromium.org>
Date: Tue Aug 28 10:25:28 2018

[tools/perf] Disable failing stories

Disable the stories:
- long_running:tools:gmail-foreground
- long_running:tools:gmail-background
- browse:news:toi
- browse:news:cnn

Failing on benchmarks:
- system_health.common_mobile
- system_health.memory_mobile
- v8.browsing_mobile

TBR=nedneguyen@google.com
NOTRY=true

Bug: 877648
Change-Id: I5f8a1170299bd98d8fea81fc54390a95a69a5350
Reviewed-on: https://chromium-review.googlesource.com/1193482
Reviewed-by: Juan Antonio Navarro Pérez <perezju@chromium.org>
Commit-Queue: Juan Antonio Navarro Pérez <perezju@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586640}
[modify] https://crrev.com/de0853f4ff4ca1438053999950702154117947b2/tools/perf/expectations.config

This is still failing on pinpoint for me with timeout exceptions:
https://chromeperf.appspot.com/report?sid=1cbaf2c79e4934f10a16a8cae7f57b46cbdf44d56bdaf312ac631e9fe09e2c0a

Is this supposed to work?

Re #12: can you post a link to the failing pinpoint job?

Oh, sorry for pasting the wrong link above, it's https://pinpoint-dot-chromeperf.appspot.com/job/12e162a9640000

+dtu, +simonhatch #14 is another instance of https://github.com/catapult-project/catapult/issues/4574

Also looks like these long running tests are also failing on N5 :( proceeding to disable there.

Issue 777355 has been merged into this issue.

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

commit bdd55eca45e137cd4c9a0fae937efe4c175aac6d
Author: Juan Antonio Navarro Perez <perezju@chromium.org>
Date: Wed Aug 29 09:49:47 2018

[tools/perf] Disable long_running:tools:gmail-* stories on all Android

Stories are also failing on all remaining Android bots.

TBR=nednguyen@google.com
NOTRY=true

Bug: 877648
Change-Id: I906b895b2a483db372a1d1bc3107cfdc80831900
Reviewed-on: https://chromium-review.googlesource.com/1193889
Reviewed-by: Juan Antonio Navarro Pérez <perezju@chromium.org>
Commit-Queue: Juan Antonio Navarro Pérez <perezju@chromium.org>
Cr-Commit-Position: refs/heads/master@{#587056}
[modify] https://crrev.com/bdd55eca45e137cd4c9a0fae937efe4c175aac6d/tools/perf/expectations.config

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/13acaaa9640000

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/13acaaa9640000

All of the runs failed. The most common error (14/20 runs) was:
TimeoutException: 

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/17bed4d6140000

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/17bed4d6140000

All of the runs failed. The most common error (20/20 runs) was:
SwarmingTaskError: The swarming task failed with state "BOT_DIED".

+dtu, +stgao - pinpoint keeps failing

For BOT_DIED, I've filed issue 916877