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

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


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

chromium-rel-win7-gpu-nvidia

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

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

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : angle_perftests
  Metric       : DrawCallPerf_d3d11/score

Revision             Result                  N
chromium@457749      3078.19 +- 11.3683      21      good
chromium@457866      3078.05 +- 11.6169      21      bad

To Run This Test
  .\src\out\Release_x64\angle_perftests.exe --test-launcher-print-test-stdio=always --test-launcher-jobs=1

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

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


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

Nothing to take action on here.