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

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


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

android-nexus6

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

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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : thread_times.key_mobile_sites_smooth
  Metric       : thread_GPU_cpu_time_per_frame/thread_GPU_cpu_time_per_frame

Revision             Result                   N
chromium@470339      2.55606 +- 0.750524      21      good
chromium@470628      2.67414 +- 0.455805      21      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_mobile_sites_smooth

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

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


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

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

=== 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_mobile_sites_smooth
  Metric       : thread_GPU_cpu_time_per_frame/thread_GPU_cpu_time_per_frame
  Change       : 10.14% | 2.53452960217 -> 2.68054236136

Suspected Commit Range
  6 commits in range
  https://chromium.googlesource.com/chromium/src/+log/4728702c40ea16a82335d7d8c9b8d07f22141552..91088a195969f5af61f404c9f02edc622cbe373a


Revision             Result                    N
chromium@470339      2.53453 +- 0.544074       14       good
chromium@470484      2.50608 +- 0.544196       14       good
chromium@470485      ---                       ---      build failure
chromium@470486      ---                       ---      build failure
chromium@470487      ---                       ---      build failure
chromium@470488      ---                       ---      build failure
chromium@470489      ---                       ---      build failure
chromium@470490      2.66562 +- 0.418935       14       bad
chromium@470493      2.68639 +- 0.443976       14       bad
chromium@470502      2.71005 +- 0.145777       9        bad
chromium@470520      2.73279 +- 0.0807311      6        bad
chromium@470556      2.66709 +- 0.372055       9        bad
chromium@470628      2.68054 +- 0.410751       14       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_mobile_sites_smooth

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

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


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

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.