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

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


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

win-high-dpi

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

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

Please try rerunning the bisect.


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


Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : idle:power_avg/video.html?src_garden2_10s.mp4
  Change       : 4.77% | 6.88201357989 -> 6.55405205523

Revision             Result                   N
chromium@492252      6.88201 +- 0.306296      6      good
chromium@492254      6.55405 +- 0.584469      6      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=video.html.src.garden2.10s.mp4 media.tough_video_cases_tbmv2

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

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


For feedback, file a bug with component Speed>Bisection

Bisect actually saw an improvement. This doesn't look like a real regression.