Commit d48c03c8 authored by Gabriel Charette's avatar Gabriel Charette Committed by Commit Bot

[Documentation] RunAllTasksUntilIdle() is still useful in browser tests.

Deprecating was a bit too strong as this is still useful in few
browser tests (which don't have TestBrowserThreadBundle since it's a
unit test construct).

R=jam@chromium.org

Bug: 824431
Change-Id: Id1b44632aca4f02cbf579fe3fb2b0a91c2ac0ba4
Reviewed-on: https://chromium-review.googlesource.com/1054632Reviewed-by: default avatarJohn Abd-El-Malek <jam@chromium.org>
Commit-Queue: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#557888}
parent 27ec0616
...@@ -61,7 +61,8 @@ void RunAllPendingInMessageLoop(); ...@@ -61,7 +61,8 @@ void RunAllPendingInMessageLoop();
// rather than flushing entire threads. // rather than flushing entire threads.
void RunAllPendingInMessageLoop(BrowserThread::ID thread_id); void RunAllPendingInMessageLoop(BrowserThread::ID thread_id);
// Deprecated: Use TestBrowserThreadBundle::RunUntilIdle(). // Runs all tasks on the current thread and TaskScheduler threads until idle.
// Note: Prefer TestBrowserThreadBundle::RunUntilIdle() in unit tests.
void RunAllTasksUntilIdle(); void RunAllTasksUntilIdle();
// Get task to quit the given RunLoop. It allows a few generations of pending // Get task to quit the given RunLoop. It allows a few generations of pending
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment