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

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


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

android-nexus6
android-nexus7v2
chromium-rel-win10
chromium-rel-win7-gpu-nvidia
chromium-rel-win8-dual

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : blink_perf.shadow_dom
  Metric       : v1-distribution-disconnected-and-reconnected/v1-distribution-disconnected-and-reconnected


Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

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 blink_perf.shadow_dom

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

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


For feedback, file a bug with component Speed>Bisection

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/16a35d98040000

kicked off a bisect for ChromiumPerf/chromium-rel-win8-dual/blink_perf.shadow_dom / v0-content-reprojection

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/16a35d98040000