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

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


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

android-webview-nexus6

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

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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : thread_times.key_mobile_sites_smooth
  Metric       : thread_renderer_compositor_cpu_time_per_frame/http___cuteoverload.com

Revision             Result                    N
chromium@520267      1.78688 +- 0.077637       21      good
chromium@520347      1.79092 +- 0.0450493      21      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...cuteoverload.com thread_times.key_mobile_sites_smooth

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

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


For feedback, file a bug with component Speed>Bisection

Closing.  Noisy metric and at same level as prior level