Use TaskScheduler instead of SequencedWorkerPool in components/feedback.

Use TaskScheduler instead of SequencedWorkerPool in components/feedback.

SequencedWorkerPool is being deprecated in favor of TaskScheduler.

BUG=667892
R=jochen@chromium.org

Review-Url: https://codereview.chromium.org/2876213002
Cr-Commit-Position: refs/heads/master@{#473979}
Committed: https://chromium.googlesource.com/chromium/src/+/5a26691054acb3098870a6b53185dbdf3a06a92e

[fdoray, 2017-05-12 16:59:04]

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

[fdoray, 2017-05-12 16:59:05]

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 16:59:28]

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

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

[commit-bot: I haz the power, 2017-05-12 17:13:28]

Dry run: Try jobs failed on following builders:
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[fdoray, 2017-05-19 19:24:25]

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

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

Description was changed from

==========
Use TaskScheduler instead of SequencedWorkerPool in feedback.

SequencedWorkerPool is being deprecated in favor of TaskScheduler.

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

to

==========
Use TaskScheduler instead of SequencedWorkerPool in components/feedback.

SequencedWorkerPool is being deprecated in favor of TaskScheduler.

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

[commit-bot: I haz the power, 2017-05-19 19:25:29]

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-19 21:40:04]

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

[commit-bot: I haz the power, 2017-05-19 21:40:05]

Dry run: This issue passed the CQ dry run.

[jochen (gone - plz use gerrit), 2017-05-22 11:46:22]

please ask a feedback owner to review

[fdoray, 2017-05-23 13:54:39]

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

[fdoray, 2017-05-23 13:54:39]

PTAL

[afakhry, 2017-05-23 16:04:25]

lgtm

[fdoray, 2017-05-23 17:11:34]

The CQ bit was checked by fdoray@chromium.org

[commit-bot: I haz the power, 2017-05-23 17:12:11]

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-23 18:13:27]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1495559494588830,
"parent_rev": "b8287fc2a9d171dffb69680d559e3f2cae3c1ff5", "commit_rev":
"5a26691054acb3098870a6b53185dbdf3a06a92e"}

[commit-bot: I haz the power, 2017-05-23 18:13:37]

Description was changed from

==========
Use TaskScheduler instead of SequencedWorkerPool in components/feedback.

SequencedWorkerPool is being deprecated in favor of TaskScheduler.

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

to

==========
Use TaskScheduler instead of SequencedWorkerPool in components/feedback.

SequencedWorkerPool is being deprecated in favor of TaskScheduler.

BUG=667892
R=jochen@chromium.org

Review-Url: https://codereview.chromium.org/2876213002
Cr-Commit-Position: refs/heads/master@{#473979}
Committed:
https://chromium.googlesource.com/chromium/src/+/5a26691054acb3098870a6b53185...
==========

[commit-bot: I haz the power, 2017-05-23 18:13:38]

Committed patchset #2 (id:20001) as
https://chromium.googlesource.com/chromium/src/+/5a26691054acb3098870a6b53185...