Use TaskScheduler instead of WorkerPool in cache_util.cc.

Use TaskScheduler instead of WorkerPool in cache_util.cc.

The following traits are used:

Priority: BACKGROUND
  User won't notice if this task takes an arbitrarily long time
  to complete.

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
Review-Url: https://codereview.chromium.org/2674163003
Cr-Commit-Position: refs/heads/master@{#453479}
Committed: https://chromium.googlesource.com/chromium/src/+/974b02737a66b77b9f58889226c5fd6f71539dce

[fdoray, 2017-02-06 20:32:07]

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

[fdoray, 2017-02-06 20:32:29]

Watch win10

[commit-bot: I haz the power, 2017-02-06 20:33:23]

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-06 21:44:53]

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

[commit-bot: I haz the power, 2017-02-06 21:44:54]

Dry run: This issue passed the CQ dry run.

[fdoray, 2017-02-07 16:16:16]

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

[fdoray, 2017-02-07 16:16:17]

PTAL

This CL previously landed as https://codereview.chromium.org/2610503002/ and was
reverted because of conflicts between multiple CLs (Scoped(Async)TaskSchedulers
was added multiple times to the same tests). This should no longer be an issue.

[fdoray, 2017-02-13 16:53:13]

On 2017/02/07 16:16:17, fdoray wrote:
> PTAL
> 
> This CL previously landed as https://codereview.chromium.org/2610503002/ and
was
> reverted because of conflicts between multiple CLs
(Scoped(Async)TaskSchedulers
> was added multiple times to the same tests). This should no longer be an
issue.

ping

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

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

[fdoray, 2017-02-24 20:27:34]

+eroman@chromium.org

PTAL

[eroman, 2017-02-27 18:00:31]

lgtm

(+jkarlin FYI for cache stuff)

[jkarlin, 2017-02-27 18:49:41]

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

[jkarlin, 2017-02-27 18:49:41]

lgtm as well

[fdoray, 2017-02-28 01:38:15]

The CQ bit was checked by fdoray@chromium.org

[commit-bot: I haz the power, 2017-02-28 01:38:58]

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-28 03:00:46]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1488245895217940, "parent_rev":
"468824d8e6ce6def7e144e9a72ae706f4b0b1b2b", "commit_rev":
"974b02737a66b77b9f58889226c5fd6f71539dce"}

[commit-bot: I haz the power, 2017-02-28 03:01:24]

Description was changed from

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

The following traits are used:

Priority: BACKGROUND
  User won't notice if this task takes an arbitrarily long time
  to complete.

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
==========

to

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

The following traits are used:

Priority: BACKGROUND
  User won't notice if this task takes an arbitrarily long time
  to complete.

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

Review-Url: https://codereview.chromium.org/2674163003
Cr-Commit-Position: refs/heads/master@{#453479}
Committed:
https://chromium.googlesource.com/chromium/src/+/974b02737a66b77b9f58889226c5...
==========

[commit-bot: I haz the power, 2017-02-28 03:01:25]

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