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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgncOIpQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg7fbRtgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg7afnqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg7dG2owsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgnYDKqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgnaPEugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgnfrUtwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgndy3pwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgnfqevwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgnbi6rQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgnbjVowoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg7dfqqQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgnYTQsQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgnf-ppwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg3cDCvQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg3YTfrgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgnemtogoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg3dqfpgoM


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

android-nexus5
android-nexus5X
android-nexus6
android-nexus7v2
android-nexus9
android-one
chromium-rel-mac-hdd
chromium-rel-mac-retina
chromium-rel-mac10
chromium-rel-mac11
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
linux-release

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

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

Hi nainar@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 : Move Layout Tree Construction code into Element::rebuildLayoutTree()
Author  : nainar
Commit description:
  
This patch uses the two dirty bits (NeedsReattachLayoutTree and
ChildNeedsReattachLayoutTree) on Node and adds the relevant
getters/setters for them.

It makes rebuildLayoutTree() public to be accessed in Document.cpp.

It also moves reattachWhitespaceSiblingsIfNeeded() to rebuildLayoutTree() and
uses dirtyBits to call either reattachLayoutTree() on node itself or call
rebuildLayoutTree() on children nodes.

Also added some comments explaining some design decisions. Will be removed
upon completion of separation.

BUG= 595137 

Review-Url: https://chromiumcodereview.appspot.com/2398293003
Cr-Commit-Position: refs/heads/master@{#426353}
Commit  : 09b7a8cf0647abca732b3718987a629d12a67fee
Date    : Thu Oct 20 00:33:46 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@426349  33.9939  1.41323   5  good
chromium@426352  35.2363  0.296607  5  good
chromium@426353  25.1237  0.281029  4  bad    <--
chromium@426354  25.2293  0.15723   5  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 659054

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.dom
Test Metric: select-single-remove/select-single-remove
Relative Change: 25.78%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/792
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997836196751791344


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

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

This patch was reverted due to bug 658322.