Chromium Code Reviews
|
|
Chromium Code Reviews
Issue
2836143002:
Use TaskScheduler instead of blocking pool in test_request_interceptor.cc. (Closed)
DescriptionUse TaskScheduler instead of blocking pool in test_request_interceptor.cc.
The blocking pool is being deprecated in favor of TaskScheduler.
BUG=667892
R=bartfab@chromium.org
Review-Url: https://codereview.chromium.org/2836143002
Cr-Commit-Position: refs/heads/master@{#467650}
Committed: https://chromium.googlesource.com/chromium/src/+/ee09af07ab13ca87f084b4fd60cd500bc55b322e
Patch Set 1 #
Messages
Total messages: 16 (9 generated)
The CQ bit was checked by fdoray@chromium.org to run a CQ dry run
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.
Dry run: CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
ping On 2017/04/24 19:40:07, fdoray wrote: > 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.
Description was changed from ========== Use TaskScheduler instead of blocking pool in test_request_interceptor.cc. The blocking pool is being deprecated in favor of TaskScheduler. BUG=667892 R=bartfab@chromium.org ========== to ========== Use TaskScheduler instead of blocking pool in test_request_interceptor.cc. The blocking pool is being deprecated in favor of TaskScheduler. BUG=667892 R=bartfab@chromium.org ==========
fdoray@chromium.org changed reviewers: + tnagel@chromium.org
+tnagel@chromium.org since bartfab is "(slow)" On 2017/04/24 19:40:07, fdoray wrote: > 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.
lgtm
The CQ bit was checked by fdoray@chromium.org
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch.
Bot data: {"patchset_id": 1, "attempt_start_ts": 1493294924103580, "parent_rev":
"e34b576533b449d23735b55136c9264ccf41c1b2", "commit_rev":
"ee09af07ab13ca87f084b4fd60cd500bc55b322e"}
Message was sent while issue was closed.
Description was changed from ========== Use TaskScheduler instead of blocking pool in test_request_interceptor.cc. The blocking pool is being deprecated in favor of TaskScheduler. BUG=667892 R=bartfab@chromium.org ========== to ========== Use TaskScheduler instead of blocking pool in test_request_interceptor.cc. The blocking pool is being deprecated in favor of TaskScheduler. BUG=667892 R=bartfab@chromium.org Review-Url: https://codereview.chromium.org/2836143002 Cr-Commit-Position: refs/heads/master@{#467650} Committed: https://chromium.googlesource.com/chromium/src/+/ee09af07ab13ca87f084b4fd60cd... ==========
Message was sent while issue was closed.
Committed patchset #1 (id:1) as https://chromium.googlesource.com/chromium/src/+/ee09af07ab13ca87f084b4fd60cd... |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
