Update from https://crrev.com/309415

Update from https://crrev.com/309415

Committed: https://chromium.googlesource.com/external/mojo/+/0461682287658c6b5d1fb6fd5eef3319774899a6

[qsr, 2014-12-22 12:08:26]

Committed patchset #1 (id:1) manually as
0461682287658c6b5d1fb6fd5eef3319774899a6.

[jamesr, 2014-12-29 23:06:27]

jamesr@chromium.org changed reviewers:
+ jamesr@chromium.org

[jamesr, 2014-12-29 23:06:28]

FYI, something in this update made it so no app using surfaces can draw.
mojo:sample_app draws, but mojo:surfaces_app or anything using views just shows
a blank window.  Debugging now...

[jamesr, 2014-12-29 23:17:41]

https://codereview.chromium.org/822713002/diff/1/cc/scheduler/scheduler_state...
File cc/scheduler/scheduler_state_machine.cc (right):

https://codereview.chromium.org/822713002/diff/1/cc/scheduler/scheduler_state...
cc/scheduler/scheduler_state_machine.cc:346: if (output_surface_state_ !=
OUTPUT_SURFACE_ACTIVE)
this is what breaks - this change doesn't interact well with the way surfaces
uses the scheduler.  I'll work on a proper fix. We should have some more sanity
checks to make sure we can draw anything in normal use.

[jamesr, 2014-12-30 00:39:57]

Fix here: https://codereview.chromium.org/827163002

[qsr, 2015-01-05 13:16:08]

On 2014/12/29 23:17:41, jamesr wrote:
>
https://codereview.chromium.org/822713002/diff/1/cc/scheduler/scheduler_state...
> File cc/scheduler/scheduler_state_machine.cc (right):
> 
>
https://codereview.chromium.org/822713002/diff/1/cc/scheduler/scheduler_state...
> cc/scheduler/scheduler_state_machine.cc:346: if (output_surface_state_ !=
> OUTPUT_SURFACE_ACTIVE)
> this is what breaks - this change doesn't interact well with the way surfaces
> uses the scheduler.  I'll work on a proper fix. We should have some more
sanity
> checks to make sure we can draw anything in normal use.

 Thanks for looking into this. Do you have an idea on how to add a test for this
kind of issues?

[jamesr, 2015-01-05 21:37:35]

I don't.  I would recommend locally trying out a few basic things
(mojo/tools/mojo_demo.sh --{browser,wm_flow}, ./sky/tools/skydb) locally when
doing a roll.  It's probably easier to just manually spot check some things than
try to construct automated tests at this stage.