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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=87e36ba578709a26a89e50e4aa97635f1651d8d7d565200b04a498b84002438f


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

android-webview-nexus6

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

=== Auto-CCing suspected CL author trchen@chromium.org ===

Hi trchen@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Tien-Ren Chen
  Commit : daa5d665bb2bf001b4a71a729a6449d7afc498fe
  Date   : Mon Aug 28 22:09:46 2017
  Subject: Migrate key_silk_cases to WPRGo

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_renderer_compositor_cpu_time_per_frame/http___jsfiddle.net_ugkd4_10_show_
  Change       : 10.04% | 1.35891662303 -> 1.49529747565

Revision             Result                    N
chromium@497886      1.35892 +- 0.0259417      6      good
chromium@497891      1.37133 +- 0.0204292      6      good
chromium@497893      1.36324 +- 0.0433092      6      good
chromium@497894      1.49542 +- 0.0315002      6      bad       <--
chromium@497896      1.49161 +- 0.010563       6      bad
chromium@497906      1.49484 +- 0.033896       6      bad
chromium@497926      1.48439 +- 0.0602255      6      bad
chromium@497966      1.4953 +- 0.0434398       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...jsfiddle.net.ugkd4.10.show. thread_times.key_silk_cases

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8969256149181618816


For feedback, file a bug with component Speed>Bisection

This is due to changes in test environment. Verified that the benchmark itself still runs properly, thus safe to rebaseline our expectation.

 Issue 762216  has been merged into this issue.