Use TaskScheduler instead of SequencedWorkerPool in shell_url_request_context_getter.mm.

Use TaskScheduler instead of SequencedWorkerPool in shell_url_request_context_getter.mm.

SequencedWorkerPool is being deprecated in favor of TaskScheduler.

BUG=667892
R=droger@chromium.org

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

[fdoray, 2017-05-12 17:48:22]

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

[fdoray, 2017-05-12 17:48:24]

Please take a look.

This CL was generated automatically.

The base::MayBlock() trait was specified for all call sites and the
base::TaskPriority::BACKGROUND trait was specified for all non-test call sites.
That may not be appropriate for your use case.

Please verify that appropriate traits were used
https://cs.chromium.org/chromium/src/base/task_scheduler/task_traits.h
If everything looks good, 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 shutdown behavior is not set explicitly (no
base::TaskShutdownBehavior)?
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. Note that the default shutdown behavior is BLOCK_SHUTDOWN in
SequencedWorkerPool and SKIP_ON_SHUTDOWN in TaskScheduler.

What if the task priority is not set explicitly (no base::TaskPriority)?
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).

[commit-bot: I haz the power, 2017-05-12 17:49:47]

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-05-12 18:35:30]

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

[commit-bot: I haz the power, 2017-05-12 18:35:31]

Dry run: This issue passed the CQ dry run.

[fdoray, 2017-05-19 19:13:29]

Description was changed from

==========
Use TaskScheduler instead of SequencedWorkerPool in
shell_url_request_context_getter.mm.

SequencedWorkerPool is being deprecated in favor of TaskScheduler.

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

to

==========
Use TaskScheduler instead of SequencedWorkerPool in
shell_url_request_context_getter.mm.

SequencedWorkerPool is being deprecated in favor of TaskScheduler.

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

[fdoray, 2017-05-19 19:13:29]

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

[fdoray, 2017-05-19 19:15:36]

On 2017/05/12 17:48:24, fdoray wrote:
> Please take a look.
> 
> This CL was generated automatically.
> 
> The base::MayBlock() trait was specified for all call sites and the
> base::TaskPriority::BACKGROUND trait was specified for all non-test call
sites.
> That may not be appropriate for your use case.
> 
> Please verify that appropriate traits were used
> https://cs.chromium.org/chromium/src/base/task_scheduler/task_traits.h
> If everything looks good, 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 shutdown behavior is not set explicitly (no
> base::TaskShutdownBehavior)?
> 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. Note that the default shutdown behavior is BLOCK_SHUTDOWN in
> SequencedWorkerPool and SKIP_ON_SHUTDOWN in TaskScheduler.
> 
> What if the task priority is not set explicitly (no base::TaskPriority)?
> 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).

+eugenebut@chromium.org (no reply from droger in 1 week)

[Eugene But (OOO till 7-30), 2017-05-19 20:33:15]

lgtm

[fdoray, 2017-05-21 15:11:18]

The CQ bit was checked by fdoray@chromium.org

[commit-bot: I haz the power, 2017-05-21 15:11:31]

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-05-21 15:22:18]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1495379478209370, "parent_rev":
"2cae1f836baed3be61df4cf38d09a6c1647a7899", "commit_rev":
"ad43ae05044b76832783b7c000e41dce4ba59de2"}

[commit-bot: I haz the power, 2017-05-21 15:22:30]

Description was changed from

==========
Use TaskScheduler instead of SequencedWorkerPool in
shell_url_request_context_getter.mm.

SequencedWorkerPool is being deprecated in favor of TaskScheduler.

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

to

==========
Use TaskScheduler instead of SequencedWorkerPool in
shell_url_request_context_getter.mm.

SequencedWorkerPool is being deprecated in favor of TaskScheduler.

BUG=667892
R=droger@chromium.org

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

[commit-bot: I haz the power, 2017-05-21 15:22:31]

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