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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg65vhrAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg64L_vAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg6_6LsQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg6_6fqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg67DSogoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg6_ncrAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgq4iCngsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg6_PqpAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg69jynQoM


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

android-nexus5
android-nexus6
android-nexus9
android-one

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@433429  2.9779   6.10308  25  good
chromium@433443  3.31257  6.8215   25  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 667342

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.simple_mobile_sites
Test Metric: thread_IO_cpu_time_per_frame/thread_IO_cpu_time_per_frame
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4359
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995365536389645312


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

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

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

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@433429  12.193   18.741   25  good
chromium@433452  12.8129  20.4601  25  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 667342

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.simple_mobile_sites
Test Metric: thread_total_fast_path_cpu_time_per_frame/thread_total_fast_path_cpu_time_per_frame
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4371
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995272318163828944


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

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@433429  2.93669  4.15347  25  good
chromium@433452  3.10022  4.67593  25  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 667342

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.simple_mobile_sites
Test Metric: thread_GPU_cpu_time_per_frame/thread_GPU_cpu_time_per_frame
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4372
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995272285628746528


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

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

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_IO_cpu_time_per_frame/thread_IO_cpu_time_per_frame

Revision             Result                 N
chromium@433429      2.9779 +- 6.10308      25      good
chromium@433443      3.31257 +- 6.8215      25      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.simple_mobile_sites

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982651620901420240

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5228152782061568


| 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 Speed>Bisection.  Thank you!

Twelve of the 13 plots recovered in the last 6 months except for:
ChromiumPerf/android-nexus6/thread_times.simple_mobile_sites / thread_total_fast_path_cpu_time_per_frame

But this one have seen too many ups/downs in these months, so the old regression seems meaningless.