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

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


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

android-nexus7v2

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

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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N   Good?
chromium@428921  95.4744  1.05954   18  good
chromium@428960  95.8436  0.899555  18  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 663082

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: percentage_smooth/http___techcrunch.com
Relative Change: 0.30%
Score: 0

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


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

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

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


===== SUSPECTED CL(s) =====
Subject : Getting rid of DelegatedFrameData
Author  : samans
Commit description:
  
Note: From now on, the concept of "null" compositor frame (a compositor frame with a null delegated frame data) is gone. You should use base::Optional<CompositorFrame> instead.

BUG= 653741 

Review-Url: https://codereview.chromium.org/2449853004
Cr-Commit-Position: refs/heads/master@{#428591}
Commit  : 4ba3a0e9d06bf66b3d900fec44bcf8ee4a2964a2
Date    : Sat Oct 29 02:32:05 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@428280  98.0267  0.85228   5  good
chromium@428481  98.4055  0.540014  5  good
chromium@428582  98.2102  0.619574  5  good
chromium@428589  97.9431  0.676355  8  good
chromium@428590  97.5157  0.756115  8  good
chromium@428591  95.2444  1.41645   5  bad    <--
chromium@428592  95.6525  0.791427  5  bad
chromium@428595  95.9666  0.536827  5  bad
chromium@428607  95.0702  0.434622  5  bad
chromium@428632  95.847   0.818803  5  bad
chromium@428682  94.9423  0.966884  5  bad
chromium@429083  96.0788  1.18725   8  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 663082

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...techcrunch.com smoothness.top_25_smooth
Test Metric: percentage_smooth/http___techcrunch.com
Relative Change: 2.23%
Score: 98.0

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


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

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