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

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


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

chromium-rel-win7-gpu-nvidia

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

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

=== Auto-CCing suspected CL author geofflang@chromium.org ===

Hi geofflang@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Geoff Lang
  Commit : 94ba36a77db9027b61c306a9718674251b7c9cb5
  Date   : Fri Apr 21 19:00:31 2017
  Subject: Only bind that native GL texture if it should be complete.

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : angle_perftests
  Metric       : Textures_gl_8_textures_5_rebind_3_state_8_mips/score
  Change       : 5.91% | 4429.16666667 -> 4167.5

Revision                              Result                  N
chromium@466630                       4429.17 +- 17.7998      6      good
chromium@466657                       4479.67 +- 90.3659      9      good
chromium@466659                       4372.78 +- 510.877      9      good
chromium@466659,angle@f6b986c8fa      4321.33 +- 73.3439      6      good
chromium@466659,angle@780612a546      4394.5 +- 16.8967       6      good
chromium@466659,angle@94ba36a77d      4047.83 +- 70.1201      6      bad       <--
chromium@466659,angle@e491578f31      4072.83 +- 84.0645      6      bad
chromium@466660                       4159.11 +- 33.1796      9      bad
chromium@466661                       4149.89 +- 111.557      9      bad
chromium@466664                       4107.17 +- 174.175      6      bad
chromium@466671                       4157.5 +- 44.8051       6      bad
chromium@466684                       4147.83 +- 28.1218      6      bad
chromium@466737                       4167.5 +- 14.543        6      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/8980607612886031616

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


| 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 JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Geoff Lang
  Commit : 94ba36a77db9027b61c306a9718674251b7c9cb5
  Date   : Fri Apr 21 19:00:31 2017
  Subject: Only bind that native GL texture if it should be complete.

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : angle_perftests
  Metric       : Textures_gl_8_textures_5_rebind_3_state_8_mips/score
  Change       : 5.76% | 4413.83333333 -> 4159.5

Revision                              Result                  N
chromium@466630                       4413.83 +- 44.9537      6      good
chromium@466657                       4464.33 +- 80.8538      6      good
chromium@466659                       4441.17 +- 61.1133      6      good
chromium@466659,angle@f6b986c8fa      4332.83 +- 26.511       6      good
chromium@466659,angle@780612a546      4401.33 +- 23.7346      6      good
chromium@466659,angle@94ba36a77d      4081.83 +- 26.7737      6      bad       <--
chromium@466659,angle@e491578f31      4080.5 +- 56.9693       6      bad
chromium@466660                       4146.0 +- 90.111        6      bad
chromium@466661                       4153.17 +- 63.9596      6      bad
chromium@466664                       4127.67 +- 121.299      6      bad
chromium@466671                       4161.83 +- 41.0711      6      bad
chromium@466684                       4144.17 +- 53.0738      6      bad
chromium@466737                       4159.5 +- 83.7108       6      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/8980607606042819088

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


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

This regression is expected, it was a correctness fix.