Use TaskScheduler instead of SequencedWorkerPool in shared_sampler_win_unittest.cc.

Use TaskScheduler instead of SequencedWorkerPool in shared_sampler_win_unittest.cc.

SequencedWorkerPool is being deprecated in favor of TaskScheduler.

BUG=667892
R=nick@chromium.org

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

[fdoray, 2017-05-12 17:26:21]

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

[fdoray, 2017-05-12 17:26:23]

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:27:43]

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:17:51]

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

[commit-bot: I haz the power, 2017-05-12 18:17:52]

Dry run: This issue passed the CQ dry run.

[fdoray, 2017-05-19 19:27:14]

Description was changed from

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

SequencedWorkerPool is being deprecated in favor of TaskScheduler.

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

to

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

SequencedWorkerPool is being deprecated in favor of TaskScheduler.

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

[fdoray, 2017-05-19 19:27:14]

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

[fdoray, 2017-05-19 19:27:45]

On 2017/05/12 17:26:23, 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).

+afakhry@chromium.org (no reply from ncarter in one week)

[afakhry, 2017-05-19 21:47:09]

lgtm

[fdoray, 2017-05-21 14:37:04]

The CQ bit was checked by fdoray@chromium.org

[commit-bot: I haz the power, 2017-05-21 14: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-05-21 15:13:59]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1495377424306000, "parent_rev":
"4ae4dc1ee1751ab8108f83049c136597143b9383", "commit_rev":
"e4d6d342c3442f90f86a10b4c6a4dc43648ff88e"}

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

Description was changed from

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

SequencedWorkerPool is being deprecated in favor of TaskScheduler.

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

to

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

SequencedWorkerPool is being deprecated in favor of TaskScheduler.

BUG=667892
R=nick@chromium.org

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

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

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