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

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


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

chromium-rel-win7-gpu-nvidia

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

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

Revision             Result                 N
chromium@447858      7657.29 +- 1249.6      21      good

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/8988484156696751376

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


| 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 Tests>AutoBisect.  Thank you!

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

Hey Simon/Oysteine, perf bisect seemed to fail with an odd result. Re-running bisect now.

re: #c5

Bisect in #c3 failed because the "bad" revision specified didn't produce the metric. I see Uniforms_gl_400_vec4_repeating: score in there, but not Uniforms_gl_400_vec4: score.

Hm, I'm not sure. I might have renamed this metric at one point, but would the bisect be tripping up on that? I'm not sure why it would have a 35% regression if the metric changed name entirely.

-oysteine@ doesn't work on bisect

Good point, if it's appearing on the dashboard then the perf tests are generating the value. Not clear why the bisect wouldn't. Off the top of my head possible differences in testing environment (would hardware make a difference in this test?, although should be same anyway), how it's run, or some sort of difference between the isolated version and the binary the bisect fetches?

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

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

Revision             Result                  N
chromium@447858      7693.81 +- 1264.52      21      good

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/8988403104169987904

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


| 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 Tests>AutoBisect.  Thank you!

I'm not sure what's going on here, but I think this is noise. Tested locally.