[Device Sensors] Remove BrowserThread knowledge

content/browser/device_sensors/sensor_manager_android_unittest.cc

Index: content/browser/device_sensors/sensor_manager_android_unittest.cc
diff --git a/content/browser/device_sensors/sensor_manager_android_unittest.cc b/content/browser/device_sensors/sensor_manager_android_unittest.cc
index f773fd8023e489ceae89fe47939d8fd7c9bba5c5..98137aae84ddd156a091eadfe914d8ad18128696 100644
--- a/content/browser/device_sensors/sensor_manager_android_unittest.cc
+++ b/content/browser/device_sensors/sensor_manager_android_unittest.cc
@@ -8,8 +8,8 @@
 
 #include "base/android/jni_android.h"
 #include "base/memory/weak_ptr.h"
+#include "base/message_loop/message_loop.h"
 #include "content/browser/device_sensors/device_sensors_consts.h"
-#include "content/public/test/test_browser_thread_bundle.h"
 #include "testing/gtest/include/gtest/gtest.h"
 
 namespace content {
@@ -66,7 +66,7 @@ class AndroidSensorManagerTest : public testing::Test {
   std::unique_ptr<DeviceMotionHardwareBuffer> motion_buffer_;
   std::unique_ptr<DeviceOrientationHardwareBuffer> orientation_buffer_;
   std::unique_ptr<DeviceOrientationHardwareBuffer> orientation_absolute_buffer_;
-  content::TestBrowserThreadBundle thread_bundle_;
+  base::MessageLoop message_loop_;

[timvolodine, 2016/10/31 15:52:47]

is this needed anywhere?

[blundell, 2016/11/09 16:00:46]

It's implicitly needed by the fact that SensorManagerAndroid needs there to be a
current message loop, which there isn't by default in unittests.

 };
 
 TEST_F(AndroidSensorManagerTest, ThreeDeviceMotionSensorsActive) {