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

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


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

chromium-rel-win7-gpu-nvidia

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


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


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

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


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

Downgrading P2s that haven't been modified in more than 6 months, which have no component or owner.