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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1KGJtQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtLKfvAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1PnrpwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1MO8rgoM


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

chromium-rel-mac10
chromium-rel-mac11
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia

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

Hi jochen@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : Make it possible to set a getter and a setter at the same time
Author  : jochen
Commit description:
  
BUG=chromium:588893,  chromium:325923 
LOG=n
R=verwaest@chromium.org

Review-Url: https://codereview.chromium.org/1943303002
Cr-Commit-Position: refs/heads/master@{#36025}
Commit  : e5baec22d30dd46fb08ee38545f0d81b1f840084
Date    : Wed May 04 14:15:39 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N  Good?
chromium@391626                233.329  4.90352  5  good
chromium@391631                224.237  7.76665  5  good
chromium@391633                225.511  6.16681  5  good
chromium@391634                230.268  3.18551  5  good
chromium@391634,v8@e5baec22d3  155.824  7.89109  5  bad    <--
chromium@391634,v8@9ae91f8d77  186.127  24.3717  5  bad
chromium@391634,v8@e8e9c07e54  161.106  1.3238   5  bad
chromium@391634,v8@ca5aa3c86a  168.567  16.5298  5  bad
chromium@391635                167.153  18.8716  5  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 609581

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.bindings
Test Metric: node-list-access/node-list-access
Relative Change: 28.36%
Score: 98.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2108
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9013469754743840720


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

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

jochen@ can you check whether your CL regressed blink_perf.bindings?

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Bisect looks pretty clean and regression has not recovered. Jochen, can you take a look?

Jochen, ping on this.

the graphs have all recovered a few revisions later again.