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

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


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

android-nexus9

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@427187  2.85862  0.0641594  5  good
chromium@427196  2.86836  0.0411533  5  good
chromium@427198  2.82947  0.0283534  5  good
chromium@427200  3.0805   0.0515992  5  bad
chromium@427204  3.1746   0.0466921  5  bad
chromium@427220  3.09013  0.0875039  5  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 659538

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.key_silk_cases
Test Metric: thread_GPU_cpu_time_per_frame/thread_GPU_cpu_time_per_frame
Relative Change: 8.10%
Score: 0

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


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

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

Only N9s, WontFix.

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus9_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_GPU_cpu_time_per_frame/thread_GPU_cpu_time_per_frame

Suspected Commit Range
  1 commits in range
  https://chromium.googlesource.com/chromium/src/+log/c81a083463ff9422f6b71e6c3a086295f03fde78..26c35c2e81f97a5b291ebd4d639fc3f1a4cc50e8


Revision             Result                    N
chromium@427187      2.85862 +- 0.0641594      5      good
chromium@427196      2.86836 +- 0.0411533      5      good
chromium@427198      2.82947 +- 0.0283534      5      good
chromium@427200      3.0805 +- 0.0515992       5      bad
chromium@427204      3.1746 +- 0.0466921       5      bad
chromium@427220      3.09013 +- 0.0875039      5      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.key_silk_cases

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

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


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