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

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


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

chromium-rel-mac-hdd

2016-04-09 03:47:42 
===== BISECT JOB RESULTS =====
Status: started


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@385305         417.332264  0.684058    5           good
chromium@385310         412.873531  4.707145    4           good
chromium@385312         416.571606  4.526319    4           good
chromium@385312,v8@99eea1e109379.516707  6.081575    5           bad
chromium@385312,v8@0ce296f180381.59684   0.976288    5           bad
chromium@385312,v8@b527ec119f371.991286  1.379549    5           bad
chromium@385312,v8@823224f3ee368.710751  5.907068    5           bad
chromium@385313         371.266082  1.662347    5           bad
chromium@385314         371.68769   1.79569     5           bad
chromium@385323         369.591642  3.093961    5           bad
chromium@385340         374.59124   2.193321    5           bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 601831

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --also-run-disabled-tests blink_perf.bindings
Test Metric: first-child/first-child
Relative Change: 10.24%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/473
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9015929539989268176


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

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

Based on the bisect this is either 99eea1e109b2d8b3c4cdcc94fb4b2bfe0afd2e53 or 3f92137209ce3c1d46d6498678cce0944c460b4d. 

jyan, mlippautz - any idea?

How do you see that my CL might be involved? 

My change should not affect binding performance.

All I did was disabling a test. How would that might be involved?

Not clear. All I know is that the metric moved in the time that your two patches were committed :)

Submitting some more bisects to hopefully get more clarity.

Actually, looks like it recovered with this V8 roll: https://chromium.googlesource.com/v8/v8/+log/93c9c30a..d3e55e51

Not sure what happened, but let's not worry about it.