Use TaskScheduler instead of blocking pool in safe_browsing_service.cc.

Use TaskScheduler instead of blocking pool in safe_browsing_service.cc.

The blocking pool is being deprecated in favor of TaskScheduler.

BUG=667892
R=jialiul@chromium.org

Review-Url: https://codereview.chromium.org/2833373004
Cr-Commit-Position: refs/heads/master@{#467693}
Committed: https://chromium.googlesource.com/chromium/src/+/e79777a2947a3887983485354e03c756970c7241

[fdoray, 2017-04-24 18:45:05]

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

[fdoray, 2017-04-24 18:45:06]

PTAL!

This CL was generated automatically.

Please make sure that the appropriate TaskTraits are used to post tasks.
https://cs.chromium.org/chromium/src/base/task_scheduler/task_traits.h
If everything looks good, please lgtm and CQ this CL. Otherwise, tell
us what's wrong.

Thanks!

- FAQ -

What if bots are red? Ignore this CL. A human will look at errors shortly.

What if the task priority is not set explicitly (no .WithTaskPriority())?
When there is no explicit priority, the priority is inherited from the
calling context (e.g. a task posted from a BACKGROUND task without an
explicit priority will have a BACKGROUND priority).

What if the shutdown behavior is not set explicitly
(no .WithShutdownBehavior())?
If shutdown behavior is important for a task, it should be set explicitly.
It's not necessary to specify it if you're fine with either BLOCK_SHUTDOWN
or SKIP_ON_SHUTDOWN.

[commit-bot: I haz the power, 2017-04-24 18:45:46]

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-04-24 19:47:38]

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

[commit-bot: I haz the power, 2017-04-24 19:47:38]

Dry run: This issue passed the CQ dry run.

[Jialiu Lin, 2017-04-26 18:20:45]

LGTM. Thanks for addressing this deprecation!

[fdoray, 2017-04-26 18:29:29]

The CQ bit was checked by fdoray@chromium.org

[commit-bot: I haz the power, 2017-04-26 18:30:15]

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-26 19:36:47]

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

[commit-bot: I haz the power, 2017-04-26 19:36:48]

Try jobs failed on following builders:
  linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)

[fdoray, 2017-04-27 13:36:59]

The CQ bit was checked by fdoray@chromium.org

[commit-bot: I haz the power, 2017-04-27 13:37:15]

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-27 15:50:59]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1493300219688000, "parent_rev":
"d1f8f6ca6c8b7cdaf02150099ce6db0cfc7223f6", "commit_rev":
"e79777a2947a3887983485354e03c756970c7241"}

[commit-bot: I haz the power, 2017-04-27 15:51:17]

Description was changed from

==========
Use TaskScheduler instead of blocking pool in safe_browsing_service.cc.

The blocking pool is being deprecated in favor of TaskScheduler.

BUG=667892
R=jialiul@chromium.org
==========

to

==========
Use TaskScheduler instead of blocking pool in safe_browsing_service.cc.

The blocking pool is being deprecated in favor of TaskScheduler.

BUG=667892
R=jialiul@chromium.org

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

[commit-bot: I haz the power, 2017-04-27 15:51:20]

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