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

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


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

chromium-rel-win7-gpu-nvidia

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

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


===== TESTED REVISIONS =====
Revision                       Mean   Std Dev   N  Good?
chromium@426786                207.2  0.447214  5  good
chromium@426819                208.8  0.447214  5  good
chromium@426822                208.2  1.09545   5  good
chromium@426823                208.2  0.447214  5  good
chromium@426823,v8@a8e30c0e68  208.8  0.83666   5  good
chromium@426823,v8@a4ff04ab13  208.2  0.447214  5  good
chromium@426823,v8@e31e5e91a5  202.4  0.894427  5  bad
chromium@426823,v8@dd614f55ce  202.8  0.447214  5  bad
chromium@426824                203.4  0.547723  5  bad
chromium@426828                202.8  0.83666   5  bad
chromium@426836                203.0  1.0       5  bad
chromium@426852                203.4  1.51658   5  bad

Bisect job ran on: winx64nvidia_perf_bisect
Bug ID: 659049

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

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


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

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

Strange the bot didn't finger one of the patches (v8@e31e5e91a5) I'll run it again with more iterations.

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1936
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

These regressions happened before M56 branch. M56 is now in stable. These regressions made it to the stable channel. Marking wontfix.