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

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


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

android-nexus5
linux-release

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

===== 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@419615  55.2311  0.555388  8  good
chromium@419616  55.231   0.990523  5  good
chromium@419617  58.1768  0.725547  5  bad    <--
chromium@419618  57.9225  0.773627  5  bad
chromium@419621  58.1399  1.09388   8  bad
chromium@419626  58.9334  0.553834  5  bad
chromium@419636  58.6706  0.520754  5  bad
chromium@419657  58.2356  0.628569  5  bad

Bisect job ran on: linux_perf_bisect
Bug ID: 649231

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.tough_filters_cases
Test Metric: frame_times/http___rawgit.com_WebKit_webkit_master_PerformanceTests_Animometer_developer.html?test-interval_20_display_minimal_controller_fixed_frame-rate_50_kalman-process-error_1_kalman-measurement-error_4_time-measurement_performance_suite-name_Animometer_test-name_Focus_complexity_100
Relative Change: 5.51%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6720
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000845477891208384


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

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