Use TaskScheduler instead of blocking pool in zip_file_creator.cc.

Use TaskScheduler instead of blocking pool in zip_file_creator.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: SKIP_ON_SHUTDOWN (default)
  Tasks posted with this mode that have not started executing at
  shutdown will never run. However, any task that has already begun
  executing when shutdown is invoked will be allowed to continue and
  will block shutdown until completion.

  Note: Previously, the task was posted to the blocking pool with
  BLOCK_SHUTDOWN (default in SequencedWorkerPool).

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=667892
Review-Url: https://codereview.chromium.org/2627093004
Cr-Commit-Position: refs/heads/master@{#443546}
Committed: https://chromium.googlesource.com/chromium/src/+/638112939838ea481913022c4c05232162238b33

[fdoray, 2017-01-11 21:27:32]

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

[commit-bot: I haz the power, 2017-01-11 21:28:41]

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-01-11 22:18:53]

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

[commit-bot: I haz the power, 2017-01-11 22:18:53]

Dry run: This issue passed the CQ dry run.

[fdoray, 2017-01-12 13:30:09]

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

[fdoray, 2017-01-12 13:30:10]

PTAL

Blocking pool is being deprecated in favor of TaskScheduler.

[kinaba, 2017-01-13 00:38:11]

lgtm

(Just in case CCing yawano@ and takise@ who started working on zip packer iiuc.)

[fdoray, 2017-01-13 13:03:34]

The CQ bit was checked by fdoray@chromium.org

[commit-bot: I haz the power, 2017-01-13 13:03:52]

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-01-13 13:35:17]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1484312614067520, "parent_rev":
"4ed25061887ba8183010f4cdd800dff04bcdc794", "commit_rev":
"638112939838ea481913022c4c05232162238b33"}

[commit-bot: I haz the power, 2017-01-13 13:35:47]

Description was changed from

==========
Use TaskScheduler instead of blocking pool in zip_file_creator.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: SKIP_ON_SHUTDOWN (default)
  Tasks posted with this mode that have not started executing at
  shutdown will never run. However, any task that has already begun
  executing when shutdown is invoked will be allowed to continue and
  will block shutdown until completion.

  Note: Previously, the task was posted to the blocking pool with
  BLOCK_SHUTDOWN (default in SequencedWorkerPool).

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

to

==========
Use TaskScheduler instead of blocking pool in zip_file_creator.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: SKIP_ON_SHUTDOWN (default)
  Tasks posted with this mode that have not started executing at
  shutdown will never run. However, any task that has already begun
  executing when shutdown is invoked will be allowed to continue and
  will block shutdown until completion.

  Note: Previously, the task was posted to the blocking pool with
  BLOCK_SHUTDOWN (default in SequencedWorkerPool).

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

Review-Url: https://codereview.chromium.org/2627093004
Cr-Commit-Position: refs/heads/master@{#443546}
Committed:
https://chromium.googlesource.com/chromium/src/+/638112939838ea481913022c4c05...
==========

[commit-bot: I haz the power, 2017-01-13 13:35:48]

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