All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=891262

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=99eba44b8fa26440d88ba355763e3c0b27c071ff1521cdd023f91e8c5d451147


Bot(s) for this bug's original alert(s):

Android Nexus6 WebView Perf

system_health.common_mobile - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

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

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

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/131d6b32e40000

Results in the past was a kind of binary, and at the suspected point, results start sticking to the worse bar. So, it may be difficult to say there is a clear CL that causes a regression, but let me kick another job because the last try failed with BOT_DIED error.

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

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/15b3dc81e40000

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

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/167b2a65e40000

Dave, looks like these bots have been down for a while?

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

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

This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.