Run event executor on the ui thread to remove the need to explicitly XFlush() the XTest calls.

remoting/host/chromoting_host_context_unittest.cc

Index: remoting/host/chromoting_host_context_unittest.cc
diff --git a/remoting/host/chromoting_host_context_unittest.cc b/remoting/host/chromoting_host_context_unittest.cc
index 827ad37242eea687906e74eb0bce061b0ed9251c..cf7d207612fbb7b897950020e57ecbf237e794ef 100644
--- a/remoting/host/chromoting_host_context_unittest.cc
+++ b/remoting/host/chromoting_host_context_unittest.cc
@@ -11,7 +11,7 @@ namespace remoting {
 // A simple test that starts and stop the context. This tests the context
 // operates properly and all threads and message loops are valid.
 TEST(ChromotingHostContextTest, StartAndStop) {
-  ChromotingHostContext context;
+  ChromotingHostContext context(0);

[awong, 2011/02/14 17:27:29]

Please use NULL instead of 0.

[Jamie, 2011/02/14 19:12:38]

Done.

   context.Start();
   EXPECT_TRUE(context.jingle_thread());
   EXPECT_TRUE(context.main_message_loop());