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

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


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

win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : story:power_avg/video.html?src_crowd2160.mp4

Revision             Result                  N
chromium@505653      2.25674 +- 10.9002      21      good
chromium@505742      2.96454 +- 11.3987      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=video.html.src.crowd2160.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/8966188914654452640


For feedback, file a bug with component Speed>Bisection

Data is gone, and no bisect.