Use ScopedTaskEnvironment instead of MessageLoopForUI in /ios/chrome
MessageLoopForUI will go away, eventually. ScopedTaskEnvironment will per default start a ThreadPool, which should be fine in most of the cases. If you believe your test needs to make sure that no ThreadPool runs let me know and I will update the patch. BUG=891670 This CL was uploaded by git cl split. R=droger@chromium.org Change-Id: Ieb7595218c6176d258dfbd7d83272a4b9d3704e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717291 Auto-Submit: Carlos Caballero <carlscab@google.com> Reviewed-by:Rohit Rao <rohitrao@chromium.org> Commit-Queue: Carlos Caballero <carlscab@google.com> Cr-Commit-Position: refs/heads/master@{#683110}
Showing
Please register or sign in to comment