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

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


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

chromium-rel-win7-gpu-ati

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

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

Bisect Details
  Configuration: winx64ati_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : time_to_play/video.html?src_garden2_10s.mp4

Revision             Result                  N
chromium@458881      471.307 +- 641.985      21      good
chromium@459005      492.232 +- 805.571      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.garden2.10s.mp4 media.tough_video_cases

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

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


| 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 results and original graphs appear to show this is actually in the noise.