Makes WindowTreeClientTest destroy state in TearDown

Makes WindowTreeClientTest destroy state in TearDown

Problem with waiting for destructor is at that point the MessageLoop has been destroyed, which causes problems with binding code.

BUG=598925
TEST=test only change
R=ben@chromium.org

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

[sky, 2016-04-01 16:28:12]

Description was changed from

==========
Makes ShellTest delete MessageLoop in destructor

Problem with deleting in TearDown is that some tests may have
members that are deleted from the tests destructor that expect the
messageloop to be available.
For example, deleting a SyncHandleWatcher wants to add a
DestructionObserver to the MessageLoop.

BUG=598925
TEST=test only change
R=rockot@chromium.org
==========

to

==========
Makes ShellTest delete MessageLoop in destructor

Problem with deleting in TearDown is that some tests may have
members that are deleted from the tests destructor that expect the
messageloop to be available.
For example, deleting a SyncHandleWatcher wants to add a
DestructionObserver to the MessageLoop.

BUG=598925
TEST=test only change
R=rockot@chromium.org
==========

[sky, 2016-04-01 16:28:12]

sky@chromium.org changed reviewers:
+ ben@chromium.org
- rockot@chromium.org

[sky, 2016-04-01 17:29:19]

Description was changed from

==========
Makes ShellTest delete MessageLoop in destructor

Problem with deleting in TearDown is that some tests may have
members that are deleted from the tests destructor that expect the
messageloop to be available.
For example, deleting a SyncHandleWatcher wants to add a
DestructionObserver to the MessageLoop.

BUG=598925
TEST=test only change
R=rockot@chromium.org
==========

to

==========
Makes WindowTreeClientTest destroy state in TearDown

Problem with waiting for destructor is at that point the MessageLoop has been
destroyed, which causes problems with binding code.

BUG=598925
TEST=test only change
R=ben@chromium.org
==========

[Ben Goodger (Google), 2016-04-01 18:26:09]

lgtm

[sky, 2016-04-01 19:31:01]

The CQ bit was checked by sky@chromium.org

[commit-bot: I haz the power, 2016-04-01 19:31:41]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1843333005/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1843333005/20001

[commit-bot: I haz the power, 2016-04-01 20:22:07]

Description was changed from

==========
Makes WindowTreeClientTest destroy state in TearDown

Problem with waiting for destructor is at that point the MessageLoop has been
destroyed, which causes problems with binding code.

BUG=598925
TEST=test only change
R=ben@chromium.org
==========

to

==========
Makes WindowTreeClientTest destroy state in TearDown

Problem with waiting for destructor is at that point the MessageLoop has been
destroyed, which causes problems with binding code.

BUG=598925
TEST=test only change
R=ben@chromium.org
==========

[commit-bot: I haz the power, 2016-04-01 20:22:08]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-04-01 20:23:18]

Description was changed from

==========
Makes WindowTreeClientTest destroy state in TearDown

Problem with waiting for destructor is at that point the MessageLoop has been
destroyed, which causes problems with binding code.

BUG=598925
TEST=test only change
R=ben@chromium.org
==========

to

==========
Makes WindowTreeClientTest destroy state in TearDown

Problem with waiting for destructor is at that point the MessageLoop has been
destroyed, which causes problems with binding code.

BUG=598925
TEST=test only change
R=ben@chromium.org

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

[commit-bot: I haz the power, 2016-04-01 20:23:19]

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