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

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


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

android-nexus5

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/1684a7acc40000

Pinpoint has been running for 4 days?

> Pinpoint has been running for 4 days?

Now at 6 days ;)

Simon, can you take a look? It looks like This should have failed.

Tracked this down in the logs, so what I think happened was that this job scheduled it's run() task as normal, it tried to run but was aborted with the following:

"Request was aborted after waiting too long to attempt to service your request."

AFAIK this can happen when a new instance is spun up but isn't ready before the 10s limit, leaving the job in limbo.

The swarming tasks associated with this job finished a long time ago, but haven't been picked up.

I think I can use dev_console to resurrect this, and file a github issue.

Filed a bug: https://github.com/catapult-project/catapult/issues/4408


Since I used dev_console to bring this back to life, the resulting posted comment will likely use "pinpoint.chromeperf.appspot.com' which will be wrong, just something to note.

Seems to be running now, so I'll pass thi sback.

📍 Couldn't reproduce a difference.
https://pinpoint.chromeperf.appspot.com/job/1684a7acc40000

Thanks Bisect folks!

Closing: WontFix. No repro and the original alerts are gone from the link above... probably pulled into another bug.