Use TaskScheduler instead of SequencedWorkerPool in streaming_utf8_validator_unittest.cc.

Use TaskScheduler instead of SequencedWorkerPool in streaming_utf8_validator_unittest.cc.

SequencedWorkerPool is being deprecated in favor of TaskScheduler.

BUG=667892
R=jshin@chromium.org

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

[fdoray, 2017-05-12 17:00:55]

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

[fdoray, 2017-05-12 17:00:58]

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:01:50]

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 17:19:58]

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

[commit-bot: I haz the power, 2017-05-12 17:19:59]

Dry run: This issue passed the CQ dry run.

[jungshik at Google, 2017-05-12 22:54:09]

lgtm

[fdoray, 2017-05-13 01:46:06]

The CQ bit was checked by fdoray@chromium.org

[commit-bot: I haz the power, 2017-05-13 01:46:30]

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-13 01:52:12]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1494639966109970, "parent_rev":
"ad4f5792cb064c721831860a180e4f25f99cf186", "commit_rev":
"e79ab37ea881753ebdf532441a4749d1747de091"}

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

Description was changed from

==========
Use TaskScheduler instead of SequencedWorkerPool in
streaming_utf8_validator_unittest.cc.

SequencedWorkerPool is being deprecated in favor of TaskScheduler.

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

to

==========
Use TaskScheduler instead of SequencedWorkerPool in
streaming_utf8_validator_unittest.cc.

SequencedWorkerPool is being deprecated in favor of TaskScheduler.

BUG=667892
R=jshin@chromium.org

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

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

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