Remove the --disable-begin-frame-scheduling flag

Remove the --disable-begin-frame-scheduling flag

This is on by default and appears to have stuck.  Removing this flag
allows for followup patches to remove old code that will then be dead.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel

Committed: https://crrev.com/58135d27a8d771b9cf18dd240c8f8886272ebcdc
Cr-Commit-Position: refs/heads/master@{#415516}

[enne (OOO), 2016-08-30 22:22:38]

Description was changed from

==========
Remove the --disable-begin-frame-scheduling flag

This is on by default and appears to have stuck.  Removing this flag
allows for followup patches to remove old code that will then be dead.
==========

to

==========
Remove the --disable-begin-frame-scheduling flag

This is on by default and appears to have stuck.  Removing this flag
allows for followup patches to remove old code that will then be dead.
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel
==========

[enne (OOO), 2016-08-30 22:23:25]

Description was changed from

==========
Remove the --disable-begin-frame-scheduling flag

This is on by default and appears to have stuck.  Removing this flag
allows for followup patches to remove old code that will then be dead.
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel
==========

to

==========
Remove the --disable-begin-frame-scheduling flag

This is on by default and appears to have stuck.  Removing this flag
allows for followup patches to remove old code that will then be dead.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel
==========

[enne (OOO), 2016-08-30 22:23:26]

enne@chromium.org changed reviewers:
+ piman@chromium.org

[enne (OOO), 2016-08-30 22:23:48]

The CQ bit was checked by enne@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-08-30 22:24:29]

Dry run: 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-08-30 23:25:55]

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

[commit-bot: I haz the power, 2016-08-30 23:25:55]

Dry run: This issue passed the CQ dry run.

[piman, 2016-08-31 00:23:12]

LGTM, thanks!

[enne (OOO), 2016-08-31 00:25:07]

The CQ bit was checked by enne@chromium.org

[commit-bot: I haz the power, 2016-08-31 00:25:37]

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-08-31 00:34:35]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-31 00:36:06]

Description was changed from

==========
Remove the --disable-begin-frame-scheduling flag

This is on by default and appears to have stuck.  Removing this flag
allows for followup patches to remove old code that will then be dead.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel
==========

to

==========
Remove the --disable-begin-frame-scheduling flag

This is on by default and appears to have stuck.  Removing this flag
allows for followup patches to remove old code that will then be dead.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel

Committed: https://crrev.com/58135d27a8d771b9cf18dd240c8f8886272ebcdc
Cr-Commit-Position: refs/heads/master@{#415516}
==========

[commit-bot: I haz the power, 2016-08-31 00:36:08]

Patchset 1 (id:??) landed as
https://crrev.com/58135d27a8d771b9cf18dd240c8f8886272ebcdc
Cr-Commit-Position: refs/heads/master@{#415516}