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

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


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

android-nexus5X

===== 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     Std Dev    N   Good?
chromium@396502  2.87115  0.0709768  18  good
chromium@396545  2.85467  0.0188947  18  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 615835

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.key_idle_power_cases
Test Metric: tasks_per_second_total_all/request-animation-frame.html
Relative Change: 2.38%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/187
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9011238765803648752


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

| 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: 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     Std Dev    N   Good?
chromium@396502  2.86856  0.0709452  18  good
chromium@396545  2.86011  0.0289507  18  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 615835

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.key_idle_power_cases
Test Metric: tasks_per_second_total_all/request-animation-frame.html
Relative Change: 1.72%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/188
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9011238768619201152


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

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

This is extremely weird. Seems to have regressed only on N5x on the IO thread, but not on any other device [1]
Bisects cannot repro and I inspected the CL and cannot see any evident culprit.
sullivan@ I think I'm going to put this into the cold case archives unless somebody has a better way to tell what might be going on here.

[1] https://chromeperf.appspot.com/report?sid=85e872c7897a68a4c6093fb3c979c1788a6c9aa28042780ea6c1baf5c80a9b06&start_rev=395597&end_rev=396736

Yeah, since we don't have an owner for android power not much else we can do here. It is too bad there's no reference build. I did check that this ran on the same device/OS before/after the regression.

===== 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      Std Dev      N   Good?
chromium@396502  0.297793  0.00307283   18  good
chromium@396545  0.2959    0.000639591  18  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 615835

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.key_idle_power_cases
Test Metric: tasks_per_second_IO/tasks_per_second_IO
Relative Change: 0.25%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/192
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9011150597796518944


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

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