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

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


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

android-nexus9

===== 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@379031         37474.333333156.895642  12          good
chromium@379064         37495.125   132.311794  8           bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 592746

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

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1668
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9018812554080314416


| 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!

re-kicked bisect with modified range as previous bisect job was aborted.

Last bisect failed due to a flaky device failure. Started another bisect job: https://chromeperf.appspot.com/buildbucket_job_status/9017186976129485568

Note that this alert is on only one platform and the graph looks quite noisy, and the regression hasn't been confirmed by bisect yet.

If the next green bisect job doesn't confirm this regression, then this bug should be closed.

===== 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@379031         37421.166667217.397346  12          good
chromium@379064         37452.0     140.200876  8           bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 592746

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

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1693
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9017187048250011744


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

| 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!

the previous bisect job aborted, qyearsley@ can we close this issue.

I think so, because:
 - alert is on only one platform
 - graph looks noisy
 - bisect failed to reproduce