Fix content_unittests for Ozone GBM

content/test/content_test_suite.cc

Index: content/test/content_test_suite.cc
diff --git a/content/test/content_test_suite.cc b/content/test/content_test_suite.cc
index 18a116f3e0a42765c0c6a45baf09074e30cea38e..d5bf9d4284ab86beee78effb933e3e685f34cae1 100644
--- a/content/test/content_test_suite.cc
+++ b/content/test/content_test_suite.cc
@@ -44,6 +44,10 @@
 #include "ui/gl/android/surface_texture.h"
 #endif
 
+#if defined (USE_OZONE)
+#include "base/message_loop/message_loop.h"
+#endif
+
 namespace content {
 namespace {
 
@@ -110,7 +114,9 @@ void ContentTestSuite::Initialize() {
   mock_cr_app::RegisterMockCrApp();
 #endif
 #endif
-
+#if defined(USE_OZONE)
+  base::MessageLoopForUI main_loop;

[sky, 2015/03/30 14:46:38]

None of the other platforms initialize the message loop here. Why does ozone
need to do it here and not else where like other platforms?

[vignatti (out of this project), 2015/03/30 15:01:50]

A few Ozone implementations like the GBM requires early initialization of the
message loop because GL stuff, display management and etc (most of hardware
accesses) happen in the GPU process only. So we need the message loop in place
already for the GPU process initial handshake behave correctly... ideally X11
backend ought to be like that.

I can write a comment in the code like that if you prefer.

+#endif
 #if defined(OS_WIN)
   gfx::InitDeviceScaleFactor(1.0f);
 #endif