Disable a flaky test InputRouterImplTest.AckedTouchEventState in...

Disable a flaky test InputRouterImplTest.AckedTouchEventState in content_unittests on Win, Linux and ChromiumOS

TBR=aelias@chromium.org

Bug: 728025
Change-Id: Icb1df3b7e353b4626c9ba263dd3b4c64dcd04276
Reviewed-on: https://chromium-review.googlesource.com/518783
Commit-Queue: Takeshi Yoshino <tyoshino@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#475835}

content/browser/renderer_host/input/input_router_impl_unittest.cc

@@ -1022,7 +1022,12 @@ TEST_F(InputRouterImplTest, TouchEventQueueFlush) {
 #if defined(USE_AURA)
 // Tests that the acked events have correct state. (ui::Events are used only on
 // windows and aura)
-TEST_F(InputRouterImplTest, AckedTouchEventState) {
+#if defined(OS_LINUX) || defined(OS_WIN) || defined(OS_CHROMEOS)
+#define MAYBE_AckedTouchEventState DISABLED_AckedTouchEventState
+#else
+#define MAYBE_AckedTouchEventState AckedTouchEventState
+#endif
+TEST_F(InputRouterImplTest, MAYBE_AckedTouchEventState) {
   input_router_->OnMessageReceived(ViewHostMsg_HasTouchEventHandlers(0, true));
   EXPECT_EQ(0U, GetSentMessageCountAndResetSink());
   EXPECT_TRUE(TouchEventQueueEmpty());