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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiLX2rgoM


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

android-galaxy-s5

Looks like bisect aborted prematurely. Sent another.

Bisect still not working right. Trying another one...

https://chromeperf.appspot.com/buildbucket_job_status/9014648102838309936

Re-kicked bisect with wider revision range.

Details on the below link:
----------------------------
https://chromeperf.appspot.com/group_report?bug_id=599857

Thank you!

YAB: https://chromeperf.appspot.com/buildbucket_job_status/9013035045759683280

Kicked off another bisect

Trying another bisect.

Last three bisects have failed. I filed a recipe engine issue 629559 for it.

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/1087
Failure reason: the build has failed.
Additional errors:
Either of the initial "good" or "bad" revisions failed to be tested or built.

Need to dig into this a bit more.

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

benhenry@ did you get a chance to look more into this?

Given that the blocking issue is fixed. I kicked another one.

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/1162
Failure reason: the build has failed due to infrastructure failure.

This bot has been decommissioned.

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