Use ScopedTaskEnvironment instead of MessageLoop in mojo unit tests.

Use ScopedTaskEnvironment instead of MessageLoop in mojo unit tests.

ScopedTaskEnvironment allows usage of ThreadTaskRunnerHandle and
base/task_scheduler/post_task.h within its scope. It should be
instantiated in every unit test that uses either of these APIs
(i.e. no test should instantiate a MessageLoop directly).

Motivation for ScopedTaskEnvironment can be found in:
https://docs.google.com/document/d/1QabRo8c7D9LsYY3cEcaPQbOCLo8Tu-6VLykYXyl3Pkk/edit

BUG=708584
R=gab@chromium.org
TBR=jam@chromium.org

Review-Url: https://codereview.chromium.org/2799043002
Cr-Commit-Position: refs/heads/master@{#462493}
Committed: https://chromium.googlesource.com/chromium/src/+/6e08ad229b41423e347d43c6ce2a3c46a7715976

[fdoray, 2017-04-05 19:47:33]

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

[fdoray, 2017-04-05 19:47:34]

gab@: PTAL

The change will then be TBRed to the owner.

[commit-bot: I haz the power, 2017-04-05 19:48:14]

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

[gab, 2017-04-05 20:54:43]

lgtm

[commit-bot: I haz the power, 2017-04-05 21:00:29]

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

[commit-bot: I haz the power, 2017-04-05 21:00:30]

Dry run: This issue passed the CQ dry run.

[fdoray, 2017-04-06 15:29:42]

The CQ bit was checked by fdoray@chromium.org

[commit-bot: I haz the power, 2017-04-06 15:30: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, 2017-04-06 15:48:20]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1491492582982890, "parent_rev":
"0bc320f205ad411a7ab935fa79879ff75e8a7fc9", "commit_rev":
"6e08ad229b41423e347d43c6ce2a3c46a7715976"}

[commit-bot: I haz the power, 2017-04-06 15:49:12]

Description was changed from

==========
Use ScopedTaskEnvironment instead of MessageLoop in mojo unit tests.

ScopedTaskEnvironment allows usage of ThreadTaskRunnerHandle and
base/task_scheduler/post_task.h within its scope. It should be
instantiated in every unit test that uses either of these APIs
(i.e. no test should instantiate a MessageLoop directly).

Motivation for ScopedTaskEnvironment can be found in:
https://docs.google.com/document/d/1QabRo8c7D9LsYY3cEcaPQbOCLo8Tu-6VLykYXyl3P...

BUG=708584
R=gab@chromium.org
TBR=jam@chromium.org
==========

to

==========
Use ScopedTaskEnvironment instead of MessageLoop in mojo unit tests.

ScopedTaskEnvironment allows usage of ThreadTaskRunnerHandle and
base/task_scheduler/post_task.h within its scope. It should be
instantiated in every unit test that uses either of these APIs
(i.e. no test should instantiate a MessageLoop directly).

Motivation for ScopedTaskEnvironment can be found in:
https://docs.google.com/document/d/1QabRo8c7D9LsYY3cEcaPQbOCLo8Tu-6VLykYXyl3P...

BUG=708584
R=gab@chromium.org
TBR=jam@chromium.org

Review-Url: https://codereview.chromium.org/2799043002
Cr-Commit-Position: refs/heads/master@{#462493}
Committed:
https://chromium.googlesource.com/chromium/src/+/6e08ad229b41423e347d43c6ce2a...
==========

[commit-bot: I haz the power, 2017-04-06 15:49:13]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/6e08ad229b41423e347d43c6ce2a...