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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnKL-8AoM


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

win-high-dpi

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

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

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


Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : page_cycler_v2.intl_hi_ru
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/http___ru.wikipedia.org_


To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...ru.wikipedia.org. page_cycler_v2.intl_hi_ru

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

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


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