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

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


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

android-nexus6

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2687
Failure reason: the build has failed due to infrastructure failure.

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

Blocking issue is fixed. Kicked another bisect.

===== 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@426993  0.06813   1.96794  169  good
chromium@427003  0.134623  3.48906  174  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 659041

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_other_cpu_time_per_frame/thread_other_cpu_time_per_frame
Relative Change: 97.60%

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


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

| 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/8990641468674531424

=== 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_nexus6_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_other_cpu_time_per_frame/thread_other_cpu_time_per_frame

Suspected Commit Range
  5 commits in range
  https://chromium.googlesource.com/chromium/src/+log/ad960c92315b64c662491152381b53b22c81a9c8..8d505b4368140b37b6a77727991e81280ceb5e6c


Revision             Result                       N
chromium@426993      0.0770335 +- 0.00484002      6        good
chromium@426994      ---                          ---      build failure
chromium@426995      ---                          ---      build failure
chromium@426996      ---                          ---      build failure
chromium@426997      ---                          ---      build failure
chromium@426998      0.133722 +- 0.0096375        6        bad
chromium@427003      0.13518 +- 0.0113476         6        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/8990641468674531424

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


| 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 alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.