|
|
DescriptionFlush TaskScheduler in content::RunAllBlockingPoolTasksUntilIdle().
Since all blocking pool call sites are being migrated to TaskScheduler,
it makes sense to flush TaskScheduler in
content::RunAllBlockingPoolTasksUntilIdle().
Once the blocking pool is fully deprecated,
content::RunAllBlockingPoolTasksUntilIdle() will be renamed to
content::RunAllTaskSchedulerTasksUntilidle().
BUG=667892, 697662
Review-Url: https://codereview.chromium.org/2750823002
Cr-Commit-Position: refs/heads/master@{#461440}
Committed: https://chromium.googlesource.com/chromium/src/+/b1e1115ec2ca636a0744eae2c442ef22bb844d41
Patch Set 1 #Patch Set 2 : add reference to bug #Patch Set 3 : add rununtilidle in TestTaskScheduler::FlushForTesting #
Total comments: 2
Patch Set 4 : fix test errors #Patch Set 5 : fix build error #Patch Set 6 : add missing include #Patch Set 7 : CR robliao #Patch Set 8 : fix test error #
Messages
Total messages: 41 (28 generated)
fdoray@chromium.org changed reviewers: + gab@chromium.org, robliao@chromium.org
PTAL
lgtm, please also file bug for issue reported by thakis@ on chromium-dev (if none already) and associate it with this issue.
Description was changed from ========== Flush TaskScheduler in content::RunAllBlockingPoolTasksUntilIdle(). Since all blocking pool call sites are being migrated to TaskScheduler, it makes sense to flush TaskScheduler in content::RunAllBlockingPoolTasksUntilIdle(). Once the blocking pool is fully deprecated, content::RunAllBlockingPoolTasksUntilIdle() will be renamed to content::RunAllTaskSchedulerTasksUntilidle(). BUG=667892 ========== to ========== Flush TaskScheduler in content::RunAllBlockingPoolTasksUntilIdle(). Since all blocking pool call sites are being migrated to TaskScheduler, it makes sense to flush TaskScheduler in content::RunAllBlockingPoolTasksUntilIdle(). Once the blocking pool is fully deprecated, content::RunAllBlockingPoolTasksUntilIdle() will be renamed to content::RunAllTaskSchedulerTasksUntilidle(). BUG=667892, 697662 ==========
On 2017/03/15 19:17:35, gab wrote: > lgtm, please also file bug for issue reported by thakis@ on chromium-dev (if > none already) and associate it with this issue. Done. The bug reported by thakis@ is https://crbug.com/697662. It was fixed by waiting on a specific task. This CL will avoid future errors rather than fixing this specific error.
fdoray@chromium.org changed reviewers: + sky@chromium.org
sky@: PTAL
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...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by fdoray@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from gab@chromium.org, sky@chromium.org Link to the patchset: https://codereview.chromium.org/2750823002/#ps40001 (title: "add rununtilidle in TestTaskScheduler::FlushForTesting")
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
Try jobs failed on following builders: linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
https://codereview.chromium.org/2750823002/diff/40001/content/public/test/tes... File content/public/test/test_utils.cc (right): https://codereview.chromium.org/2750823002/diff/40001/content/public/test/tes... content/public/test/test_utils.cc:161: // Flush blocking pool tasks. Remove this comment as it's stating what the next line does. Alternatively, you can have a banner comment that discusses the postcondition of this function (all inflight tasks are done at the end of this call and enumerate the sources). An interesting non-obvious comment would be why we do this with the MessageLoop in the third section as we've just dealt with the BlockingPool.
The CQ bit was checked by fdoray@chromium.org to run a CQ dry run
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: Try jobs failed on following builders: linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by fdoray@chromium.org to run a CQ dry run
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: Try jobs failed on following builders: linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by fdoray@chromium.org to run a CQ dry run
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: Try jobs failed on following builders: win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)
The CQ bit was checked by fdoray@chromium.org to run a CQ dry run
https://codereview.chromium.org/2750823002/diff/40001/content/public/test/tes... File content/public/test/test_utils.cc (right): https://codereview.chromium.org/2750823002/diff/40001/content/public/test/tes... content/public/test/test_utils.cc:161: // Flush blocking pool tasks. On 2017/03/17 01:00:14, robliao wrote: > Remove this comment as it's stating what the next line does. > > Alternatively, you can have a banner comment that discusses the postcondition of > this function (all inflight tasks are done at the end of this call and enumerate > the sources). > > An interesting non-obvious comment would be why we do this with the MessageLoop > in the third section as we've just dealt with the BlockingPool. Removed unnecessary comment. I have a few CLs to land: 1. Flush TaskScheduler in RunAllBlockingPoolTasksUntilIdle (this CL). 2. Always use an async TaskScheduler in TestBrowserThreadBundle. 3. Enable redirection of SequencedWorkerPool to TaskScheduler in TestBrowserThreadBundle. 4. Remove content::BrowserThread::GetBlockingPool()->FlushForTesting(); from this function. I'd like to wait until 4. to work on the comments in this function, because they'll have to be updated anyways.
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: Try jobs failed on following builders: linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by fdoray@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from gab@chromium.org, sky@chromium.org Link to the patchset: https://codereview.chromium.org/2750823002/#ps140001 (title: "fix test error")
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": 140001, "attempt_start_ts": 1491230306575080, "parent_rev": "9e717eb017b6ad11e6c580518a7074c6f56f6c5f", "commit_rev": "b1e1115ec2ca636a0744eae2c442ef22bb844d41"}
Message was sent while issue was closed.
Description was changed from ========== Flush TaskScheduler in content::RunAllBlockingPoolTasksUntilIdle(). Since all blocking pool call sites are being migrated to TaskScheduler, it makes sense to flush TaskScheduler in content::RunAllBlockingPoolTasksUntilIdle(). Once the blocking pool is fully deprecated, content::RunAllBlockingPoolTasksUntilIdle() will be renamed to content::RunAllTaskSchedulerTasksUntilidle(). BUG=667892, 697662 ========== to ========== Flush TaskScheduler in content::RunAllBlockingPoolTasksUntilIdle(). Since all blocking pool call sites are being migrated to TaskScheduler, it makes sense to flush TaskScheduler in content::RunAllBlockingPoolTasksUntilIdle(). Once the blocking pool is fully deprecated, content::RunAllBlockingPoolTasksUntilIdle() will be renamed to content::RunAllTaskSchedulerTasksUntilidle(). BUG=667892, 697662 Review-Url: https://codereview.chromium.org/2750823002 Cr-Commit-Position: refs/heads/master@{#461440} Committed: https://chromium.googlesource.com/chromium/src/+/b1e1115ec2ca636a0744eae2c442... ==========
Message was sent while issue was closed.
Committed patchset #8 (id:140001) as https://chromium.googlesource.com/chromium/src/+/b1e1115ec2ca636a0744eae2c442... |