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

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


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

android-nexus5

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

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


===== SUSPECTED CL(s) =====
Subject : cc: Remove estimated parent draw time from renderer
Author  : enne
Commit description:
  
This is a display scheduler only concept now that unified begin frame is
turned on.  Renderers can just use the deadline passed to them from the
top level begin frame source.

This fixes a regression from https://codereview.chromium.org/2299003002
where Android was using the incorrect parent estimated draw time of
none and so thought it had less time for frames than it did.

R=brianderson@chromium.org
BUG= 646377 
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel

Review-Url: https://codereview.chromium.org/2352823002
Cr-Commit-Position: refs/heads/master@{#419617}
Commit  : bfdea7f114aded7866981b8bfe3edd0c75155f12
Date    : Tue Sep 20 01:11:26 2016


===== TESTED REVISIONS =====
Revision         Mean    Std Dev   N  Good?
chromium@419606  6.3566  0.345477  5  good
chromium@419614  6.3642  0.127087  5  good
chromium@419616  6.399   0.382186  5  good
chromium@419617  8.241   0.357029  5  bad    <--
chromium@419618  7.9836  0.367154  5  bad
chromium@419622  7.655   0.326746  5  bad
chromium@419637  8.2126  0.237151  5  bad
chromium@419667  8.331   0.495627  5  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 648891

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: mean_input_event_latency/Wordpress
Relative Change: 31.06%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4136
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000921917589601616


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

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