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

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


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

android-nexus5X
android-nexus7v2
android-webview-nexus5X
chromium-rel-win10

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : thread_times.key_mobile_sites_smooth
  Metric       : thread_browser_cpu_time_per_frame/http___www.boingboing.net


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 --story-filter=http...www.boingboing.net 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/8967445964255837712


For feedback, file a bug with component Speed>Bisection

All regressions in this bug have recovered. Given the regression range I am almost certain it is a duplicate of 768336.