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

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


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

android-nexus6

Only one change in the range, a56f16d1e111284a092d28ff79963302fd092e6a. reveman, can you please investigate?

===== 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@386316         34496.75    1810.69874  8           good
chromium@386317         35171.363636178.067556  11          bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 602309

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

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2122
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9015661829437623872


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=602309

| 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 component Tests>AutoBisect.  Thank you!

re-kicked bisect with modified range.

Something is really weird here. reveman's change was not reverted, but the value went back down to original levels, and then spiked back up again. Ref build did not move. No regressions on any other devices, or on newer more reliable tests from memory infra. WontFixing.