Remove some usage of base::MessageLoopCurrent::SetTaskRunner() in tests.
This is an expanded and leak-fixed reland of crrev.com/c/1177641 and crrev.com/c/1176894, though it tackles the root of the problem rather than working around it. base::MessageLoopCurrent::SetTaskRunner() is deprecated since only owners of the MessageLoop instance should replace its TaskRunner. Odd things happen in tests when the message loop task runner is replaced and a profile is instantiated. This CL removes some more usage of the method in tests where there is interaction with a TestingProfile object. BUG=616447 Change-Id: Ic2ad6eb2a8699f103e432af74ad9c71c1dd43656 Reviewed-on: https://chromium-review.googlesource.com/1179111 Commit-Queue: Dominick Ng <dominickn@chromium.org> Reviewed-by:Greg Thompson <grt@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#584249}
Showing
Please register or sign in to comment