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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICglOXFrgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1ICvvAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1MDYowoM


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

android-nexus5

Kicked off a bisect.

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Trying another bisect.

This issue has been moved once and is lower than Pri-1. Removing the milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9006594811796192928

sullivan@, there is a regression here and never been recovered since then. The bisect failed every time because of a build failure. Do you think this bot is not working?

There is a bug in bisecting cc_perftests but I can't find it. I know dtu@ is working on it, so assigning to him to block this on fixing cc_perftests bisect.

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005126245806405632

-> sullivan to deploy perf dashboard

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/3940
Failure reason: the build has failed due to infrastructure failure.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005060838515921680

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/3940
Failure reason: the build has failed due to infrastructure failure.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9004969234358381680

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/3942
Failure reason: the build has failed due to infrastructure failure.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9004326937863777744

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/3942
Failure reason: the build has failed due to infrastructure failure.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

Perf sheriff ping

Probably still worth investigating; blocked on  issue 632890 .

Also, this appears to be the same as  issue 608476  (graphs look similar, revision range overlaps)