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

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


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

android-galaxy-s5

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@382263         847.017901  14.344243   9           good
chromium@382272         851.051111  10.716971   8           bad

Bisect job ran on: android_s5_perf_bisect
Bug ID: 596824

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests page_cycler.morejs
Test Metric: warm_times/page_load_time
Relative Change: 0.61%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/532
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9017496522248933728


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with label Cr-Tests-AutoBisect.  Thank you!

Pn a closer look, the ref changed at the same time.  We can close this.