Use TaskScheduler instead of WorkerPool in client_cert_resolver.cc.

Use TaskScheduler instead of WorkerPool in client_cert_resolver.cc.

The following traits are used:

Priority: Inherited (default)
  The priority is inherited from the calling context (i.e. TaskTraits
  are initialized with the priority of the current task).

Shutdown behavior: CONTINUE_ON_SHUTDOWN
  Tasks posted with this mode which have not started executing before
  shutdown is initiated will never run. Tasks with this mode running at
  shutdown will be ignored (the worker will not be joined).

  Note: Tasks that were previously posted to base::WorkerPool should
  use this shutdown behavior because this is how base::WorkerPool
  handles all its tasks.

May Block:
  Tasks posted with MayBlock() may block. This includes but is not
  limited to tasks that wait on synchronous file I/O operations:
  read or write a file from disk, interact with a pipe or a socket,
  rename or delete a file, enumerate files in a directory, etc. This
  trait isn't required for the mere use of locks.

BUG=659191
wip

Review-Url: https://codereview.chromium.org/2608073003
Cr-Commit-Position: refs/heads/master@{#447836}
Committed: https://chromium.googlesource.com/chromium/src/+/137677f4e89b62bb98c8007ee3eb9d9e26de1302

[fdoray, 2016-12-31 20:59:30]

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

[commit-bot: I haz the power, 2016-12-31 20:59:35]

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-12-31 21:36:44]

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

[commit-bot: I haz the power, 2016-12-31 21:36:45]

Dry run: This issue passed the CQ dry run.

[fdoray, 2017-01-01 19:13:09]

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

[fdoray, 2017-01-01 19:13:10]

PTAL. WorkerPool is being deprecated in favor of TaskScheduler.

[fdoray, 2017-02-02 17:58:18]

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

[fdoray, 2017-02-02 17:58:18]

+stevenjb@chromium.org: PTAL (no reply from cschuet after 1 month)

[stevenjb, 2017-02-02 18:25:42]

lgtm

[fdoray, 2017-02-02 19:58:12]

The CQ bit was checked by fdoray@chromium.org

[commit-bot: I haz the power, 2017-02-02 19:58:39]

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-02 20:52:19]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1486065492916530, "parent_rev":
"6270410d41cb73f7251746afaa93798e62b54555", "commit_rev":
"137677f4e89b62bb98c8007ee3eb9d9e26de1302"}

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

Description was changed from

==========
Use TaskScheduler instead of WorkerPool in client_cert_resolver.cc.

The following traits are used:

Priority: Inherited (default)
  The priority is inherited from the calling context (i.e. TaskTraits
  are initialized with the priority of the current task).

Shutdown behavior: CONTINUE_ON_SHUTDOWN
  Tasks posted with this mode which have not started executing before
  shutdown is initiated will never run. Tasks with this mode running at
  shutdown will be ignored (the worker will not be joined).

  Note: Tasks that were previously posted to base::WorkerPool should
  use this shutdown behavior because this is how base::WorkerPool
  handles all its tasks.

May Block:
  Tasks posted with MayBlock() may block. This includes but is not
  limited to tasks that wait on synchronous file I/O operations:
  read or write a file from disk, interact with a pipe or a socket,
  rename or delete a file, enumerate files in a directory, etc. This
  trait isn't required for the mere use of locks.

BUG=659191

wip
==========

to

==========
Use TaskScheduler instead of WorkerPool in client_cert_resolver.cc.

The following traits are used:

Priority: Inherited (default)
  The priority is inherited from the calling context (i.e. TaskTraits
  are initialized with the priority of the current task).

Shutdown behavior: CONTINUE_ON_SHUTDOWN
  Tasks posted with this mode which have not started executing before
  shutdown is initiated will never run. Tasks with this mode running at
  shutdown will be ignored (the worker will not be joined).

  Note: Tasks that were previously posted to base::WorkerPool should
  use this shutdown behavior because this is how base::WorkerPool
  handles all its tasks.

May Block:
  Tasks posted with MayBlock() may block. This includes but is not
  limited to tasks that wait on synchronous file I/O operations:
  read or write a file from disk, interact with a pipe or a socket,
  rename or delete a file, enumerate files in a directory, etc. This
  trait isn't required for the mere use of locks.

BUG=659191

wip

Review-Url: https://codereview.chromium.org/2608073003
Cr-Commit-Position: refs/heads/master@{#447836}
Committed:
https://chromium.googlesource.com/chromium/src/+/137677f4e89b62bb98c8007ee3eb...
==========

[commit-bot: I haz the power, 2017-02-02 20:53:04]

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