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

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


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

win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : media.desktop
  Metric       : story:power_avg/video.html?src_crowd.ogg_type_audio

Revision             Result                  N
chromium@512003      8.39341 +- 1.42315      21      good
chromium@512106      8.43483 +- 1.25768      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.crowd.ogg.type.audio media.desktop

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

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


For feedback, file a bug with component Speed>Bisection

no bisect, closing as WontFix.

+charliea@: not sure why the bisect and the continuous bots aren't matching up here. Power usage rose from ~8 watts to ~11 watts. +Randy for de-noising.

Yea, I strongly suspect that this is the issue where the ref build didn't quite meet the regression threshold but the non-ref did, so we alerted. Sigh.