Add missing unit test initialization in DeviceStatusCollectorTest.
Unlike CloudPrintProxyPolicyStartupTest, which similarly is a unit test running in the browser_tests binary, DeviceStatusCollectorTest does not initialize a ContentClient or a BrowserContentClient. This is causing tests to fail while trying to land crrev.com/c/1157704, where a new AfterStartupTask that eventually calls into a nullptr BrowserContentClient while running this seemingly unrelated test. BUG=None Change-Id: Ibb4c4a9d4b8d8ecf2e243a81158341824ef4cda1 Reviewed-on: https://chromium-review.googlesource.com/1160072 Commit-Queue: Dominick Ng <dominickn@chromium.org> Reviewed-by:Maksim Ivanov <emaxx@chromium.org> Cr-Commit-Position: refs/heads/master@{#580523}
Showing
Please register or sign in to comment