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

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


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

win-high-dpi

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

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : page_cycler_v2.basic_oopif
  Metric       : timeToFirstContentfulPaint_avg/pcv1-warm/http___booking.com

Revision             Result                  N
chromium@469200      146.352 +- 19.6712      21      good
chromium@469293      148.891 +- 27.1065      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...booking.com page_cycler_v2.basic_oopif

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

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


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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : page_cycler_v2.basic_oopif
  Metric       : timeToFirstContentfulPaint_avg/pcv1-warm/http___booking.com

Revision             Result                  N
chromium@469200      147.681 +- 18.8132      21      good
chromium@469293      148.39 +- 16.3795       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...booking.com page_cycler_v2.basic_oopif

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

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


| 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/8980148806926667328

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : page_cycler_v2.basic_oopif
  Metric       : timeToFirstContentfulPaint_avg/pcv1-warm/http___booking.com

Revision             Result                  N
chromium@469200      148.151 +- 20.2441      21      good
chromium@469293      152.032 +- 32.2988      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...booking.com page_cycler_v2.basic_oopif

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

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


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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: BUILD_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 543cbcbb37d29652edb36adcb64e1dee09e4efe8
  bad_revision : 070b9d4999b7617e092b3f47ef4f936446f9612b

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : page_cycler_v2.basic_oopif
  Metric       : timeToFirstContentfulPaint_avg/pcv1-warm/http___booking.com
  Change       : 4.11% | 145.257571429 -> 151.084714286

Revision             Result                  N
chromium@469200      145.258 +- 16.1617      14       good
---                  ---                     ---      too many build failures to list
chromium@469211      ---                     ---      build failure
chromium@469212      151.03 +- 20.3622       14       bad
chromium@469222      152.51 +- 24.6702       14       bad
chromium@469246      152.633 +- 39.6509      21       bad
chromium@469293      151.085 +- 25.2302      14       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...booking.com page_cycler_v2.basic_oopif

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

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


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