cc: Remove estimated parent draw time from renderer

cc: Remove estimated parent draw time from renderer

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

Committed: https://crrev.com/bfdea7f114aded7866981b8bfe3edd0c75155f12
Cr-Commit-Position: refs/heads/master@{#419617}

[enne (OOO), 2016-09-19 18:44:55]

Description was changed from

==========
cc: Remove estimated parent draw time from renderer

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.

R=brianderson@chromium.org
==========

to

==========
cc: Remove estimated parent draw time from renderer

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.

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

[enne (OOO), 2016-09-19 18:56:03]

Description was changed from

==========
cc: Remove estimated parent draw time from renderer

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.

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

to

==========
cc: Remove estimated parent draw time from renderer

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

[brianderson, 2016-09-19 20:47:46]

lgtm!

[enne (OOO), 2016-09-19 21:48:40]

The CQ bit was checked by enne@chromium.org

[commit-bot: I haz the power, 2016-09-19 21:49:05]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-19 21:51:50]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-19 21:51:51]

Try jobs failed on following builders:
  ios-device on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)
  ios-simulator on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/bui...)
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[enne (OOO), 2016-09-19 21:57:07]

The CQ bit was checked by enne@chromium.org

[enne (OOO), 2016-09-19 21:57:09]

The patchset sent to the CQ was uploaded after l-g-t-m from
brianderson@chromium.org
Link to the patchset: https://codereview.chromium.org/2352823002/#ps20001
(title: "Rebase")

[commit-bot: I haz the power, 2016-09-19 21:57:48]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-20 01:09:45]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-09-20 01:11:34]

Description was changed from

==========
cc: Remove estimated parent draw time from renderer

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

to

==========
cc: Remove estimated parent draw time from renderer

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

Committed: https://crrev.com/bfdea7f114aded7866981b8bfe3edd0c75155f12
Cr-Commit-Position: refs/heads/master@{#419617}
==========

[commit-bot: I haz the power, 2016-09-20 01:11:35]

Patchset 2 (id:??) landed as
https://crrev.com/bfdea7f114aded7866981b8bfe3edd0c75155f12
Cr-Commit-Position: refs/heads/master@{#419617}