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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6qOn7woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmpKL7goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6q7XkwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6tvHrAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmua38AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmo6argoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmqb8rAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmoi9rQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6pTAigkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6qS09woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6rHwsQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6oK1lgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmqzEogoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmsz6uQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6pusugsM


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

android-webview-nexus6
chromium-rel-mac11-pro
chromium-rel-win8-dual
win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : page_cycler_v2.intl_ko_th_vi
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___vnexpress.net_

Revision             Result                N
chromium@471258      278.45 +- 83.844      21      good
chromium@471298      278.8 +- 82.7001      21      bad

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...vnexpress.net. page_cycler_v2.intl_ko_th_vi

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

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


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

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : page_cycler_v2.intl_ko_th_vi
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___vnexpress.net_

Revision             Result                  N
chromium@471258      283.411 +- 97.5069      21      good
chromium@471298      278.509 +- 84.4963      21      bad

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...vnexpress.net. page_cycler_v2.intl_ko_th_vi

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

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


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