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

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


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

android-nexus7v2

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@428285  133.481  0.766604  5  good
chromium@428295  120.061  3.09055   5  bad
chromium@428305  116.646  6.03436   5  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 661545

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.bindings
Test Metric: undefined-id-getter/undefined-id-getter
Relative Change: 12.61%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3444
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997106499651877440


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

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@428285  129.071  3.73312   5  good
chromium@428290  133.291  0.38597   5  good
chromium@428292  116.055  9.61144   5  bad
chromium@428293  121.524  0.492801  5  bad
chromium@428295  119.787  3.86867   5  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 661545

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.bindings
Test Metric: undefined-id-getter/undefined-id-getter
Relative Change: 7.19%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3450
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8996918030511080128


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

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

Graph recovered.

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

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : blink_perf.bindings
  Metric       : undefined-id-getter/undefined-id-getter

Suspected Commit Range
  1 commits in range
  https://chromium.googlesource.com/chromium/src/+log/13589faa74b1c1c8ab1b1849903b0585ef09f922..25ae3ed9629d84537e1d23d24fbb1acd79d46073


Revision             Result                   N
chromium@428285      133.481 +- 0.766604      5      good
chromium@428295      120.061 +- 3.09055       5      bad
chromium@428305      116.646 +- 6.03436       5      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.bindings

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982607792497626656

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


| 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 Speed>Bisection.  Thank you!

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

Hi ikilpatrick@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : ikilpatrick
  Commit : 631ba4493ab55194d0ed2e2482c296f0aeadcb94
  Date   : Fri Oct 28 05:23:57 2016
  Subject: [LayoutNG] Remove last NGConstraintSpace constructor.

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : blink_perf.bindings
  Metric       : undefined-id-getter/undefined-id-getter
  Change       : 9.79% | 128.985262994 -> 116.35870618

Revision             Result                  N
chromium@428285      128.985 +- 22.8456      10      good
chromium@428290      131.546 +- 7.00481      6       good
chromium@428291      130.67 +- 10.64         6       good
chromium@428292      117.71 +- 13.989        6       bad       <--
chromium@428293      117.667 +- 7.52167      6       bad
chromium@428295      116.359 +- 22.2865      9       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.bindings

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982580558942087280

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


| 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 Speed>Bisection.  Thank you!