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

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


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

chromium-rel-win7-gpu-nvidia

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

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N   Good?
chromium@417965  205.167  0.834847  12  good
chromium@418000  205.167  0.834847  12  good
chromium@418017  205.417  0.792961  12  good
chromium@418026  205.222  1.28103   27  good
chromium@418030  204.963  0.854017  27  good
chromium@418032  204.963  1.09128   27  good
chromium@418034  204.111  1.07861   18  bad

Bisect job ran on: winx64nvidia_perf_bisect
Bug ID: 647619

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests jetstream
Test Metric: Score/Score
Relative Change: 0.49%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1868
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9001371227111198864


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5881751673503744

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

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N   Good?
chromium@417965  204.222  0.942809  18  good
chromium@418034  203.889  1.02262   18  bad

Bisect job ran on: winx64nvidia_perf_bisect
Bug ID: 647619

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests jetstream
Test Metric: Score/Score
Relative Change: 0.49%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1874
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000819131236509920


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5783691555504128

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

perf sheriff fixit: unsetting owners of bugs owned by sheriffs to clarify the sheriffing rotation triages the bugs.

Archiving as bisection is difficult and there's been no movement.