Fix TaskScheduler initialization in remoting processes.

Fix TaskScheduler initialization in remoting processes.

TaskScheduler was not initialized in ios::AppRuntime because
of an inverted condition.

TaskScheduler was never shutdown in remoting processes.

BUG=659191
Review-Url: https://codereview.chromium.org/2679293002
Cr-Commit-Position: refs/heads/master@{#449043}
Committed: https://chromium.googlesource.com/chromium/src/+/a1c82ce5d3aa4bb7401cc533a3538b8db6808d38

[fdoray, 2017-02-07 20:33:24]

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

[commit-bot: I haz the power, 2017-02-07 20:34:19]

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, 2017-02-07 20:48:02]

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

[commit-bot: I haz the power, 2017-02-07 20:48:03]

Dry run: This issue passed the CQ dry run.

[fdoray, 2017-02-08 13:20:45]

Description was changed from

==========
Fix TaskScheduler initialization in remoting processes.

BUG=
==========

to

==========
Fix TaskScheduler initialization in remoting processes.

TaskScheduler was not initialized in ios::AppRuntime because
of an inverted condition.

TaskScheduler was never shutdown in remoting processes.

BUG=659191
==========

[fdoray, 2017-02-08 13:22:43]

fdoray@chromium.org changed reviewers:
+ sergeyu@chromium.org

[fdoray, 2017-02-08 13:22:44]

PTAL

https://codereview.chromium.org/2679293002/diff/1/remoting/client/ios/app_run...
File remoting/client/ios/app_runtime.cc (right):

https://codereview.chromium.org/2679293002/diff/1/remoting/client/ios/app_run...
remoting/client/ios/app_runtime.cc:53: // TODO(nicholss): Shutdown the app.
Since multiple AppRuntimes can live in the same process, it would be incorrect
to shutdown TaskScheduler here. It's not so bad, it just means that shutdown
behaviors won't be honored
https://cs.chromium.org/chromium/src/base/task_scheduler/task_traits.h?l=41

https://codereview.chromium.org/2679293002/diff/1/remoting/client/jni/chromot...
File remoting/client/jni/chromoting_jni_runtime.cc (right):

https://codereview.chromium.org/2679293002/diff/1/remoting/client/jni/chromot...
remoting/client/jni/chromoting_jni_runtime.cc:115: // Block until tasks blocking
shutdown have completed their execution.
See https://cs.chromium.org/chromium/src/base/task_scheduler/task_traits.h?l=41

[Sergey Ulanov, 2017-02-08 18:34:13]

LGTM. Thanks!

[fdoray, 2017-02-08 18:37:54]

The CQ bit was checked by fdoray@chromium.org

[commit-bot: I haz the power, 2017-02-08 18:38:30]

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-02-08 18:45:35]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1486579074261520, "parent_rev":
"f92989bca70381b4b55859648a18e7871892c49b", "commit_rev":
"a1c82ce5d3aa4bb7401cc533a3538b8db6808d38"}

[commit-bot: I haz the power, 2017-02-08 18:46:16]

Description was changed from

==========
Fix TaskScheduler initialization in remoting processes.

TaskScheduler was not initialized in ios::AppRuntime because
of an inverted condition.

TaskScheduler was never shutdown in remoting processes.

BUG=659191
==========

to

==========
Fix TaskScheduler initialization in remoting processes.

TaskScheduler was not initialized in ios::AppRuntime because
of an inverted condition.

TaskScheduler was never shutdown in remoting processes.

BUG=659191

Review-Url: https://codereview.chromium.org/2679293002
Cr-Commit-Position: refs/heads/master@{#449043}
Committed:
https://chromium.googlesource.com/chromium/src/+/a1c82ce5d3aa4bb7401cc533a353...
==========

[commit-bot: I haz the power, 2017-02-08 18:46:17]

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