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

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


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

win-zenbook

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

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

Bisect Details
  Configuration: winx64_zen_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : time_to_play/crowd.wav

Revision             Result                  N
chromium@458374      79.8681 +- 46.7145      21      good
chromium@458501      76.6581 +- 26.5175      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 media.tough_video_cases

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

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


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