Disable tests broken by WK r118001

chrome/browser/browser_keyevents_browsertest.cc

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "build/build_config.h"
 
 #include "base/basictypes.h"
 #include "base/logging.h"
 #include "base/message_loop.h"
 #include "base/stringprintf.h"
@@ skipping 275 matching lines @@
       desc.append(data.result[i]);
       desc.append("\n");
     }
     return desc;
   }
 };
 
 #if defined(OS_MACOSX)
 // http://crbug.com/81451
 IN_PROC_BROWSER_TEST_F(BrowserKeyEventsTest, DISABLED_NormalKeyEvents) {
+#elif defined(OS_LINUX)

[vandebo (ex-Chrome), 2012/05/22 23:03:49]

This stuff is more commonly done with a MAYBE pattern see for example
base/synchronization/waitable_event_watcher_unittest.cc:165

[jsbell, 2012/05/22 23:18:12]

Yeah, initially I wanted a less intrusive change but you're right it's more
readable this way.

One more look?

+// http://crbug.com/129235
+IN_PROC_BROWSER_TEST_F(BrowserKeyEventsTest, FAILS_NormalKeyEvents) {
 #else
 IN_PROC_BROWSER_TEST_F(BrowserKeyEventsTest, NormalKeyEvents) {
 #endif
 
   static const KeyEventTestData kTestNoInput[] = {
     // a
     { ui::VKEY_A, false, false, false, false,
       false, false, false, false, 3,
       { "D 65 0 false false false false",
         "P 97 97 false false false false",
@@ skipping 79 matching lines @@
   ASSERT_NO_FATAL_FAILURE(SetFocusedElement(tab_index, L"B"));
   for (size_t i = 0; i < arraysize(kTestWithInput); ++i) {
     EXPECT_NO_FATAL_FAILURE(TestKeyEvent(tab_index, kTestWithInput[i]))
         << "kTestWithInput[" << i << "] in password box failed:\n"
         << GetTestDataDescription(kTestWithInput[i]);
   }
   EXPECT_NO_FATAL_FAILURE(CheckTextBoxValue(tab_index, L"B", L"aA"));
 }
 
 #if defined(OS_WIN) || defined(OS_LINUX)
+#if defined(OS_LINUX)
+// http://crbug.com/129235
+IN_PROC_BROWSER_TEST_F(BrowserKeyEventsTest, FAILS_CtrlKeyEvents) {
+#else
 IN_PROC_BROWSER_TEST_F(BrowserKeyEventsTest, CtrlKeyEvents) {
+#endif
   static const KeyEventTestData kTestCtrlF = {
     ui::VKEY_F, true, false, false, false,
     false, false, false, false, 2,
     { "D 17 0 true false false false",
       "D 70 0 true false false false" }
   };
 
   static const KeyEventTestData kTestCtrlFSuppressKeyDown = {
     ui::VKEY_F, true, false, false, false,
     true, false, false, false, 4,
@@ skipping 102 matching lines @@
 
   // Press Cmd+F with keydown suppressed shall not open the find box.
   EXPECT_NO_FATAL_FAILURE(TestKeyEvent(tab_index, kTestCmdFSuppressKeyDown));
   ASSERT_TRUE(IsViewFocused(VIEW_ID_TAB_CONTAINER));
 }
 #endif
 
 #if defined(OS_MACOSX)
 // http://crbug.com/81451 for mac
 IN_PROC_BROWSER_TEST_F(BrowserKeyEventsTest, DISABLED_AccessKeys) {
+#elif defined(OS_LINUX)
+// http://crbug.com/129235
+IN_PROC_BROWSER_TEST_F(BrowserKeyEventsTest, FAILS_AccessKeyEvents) {
 #else
 IN_PROC_BROWSER_TEST_F(BrowserKeyEventsTest, AccessKeys) {
 #endif
 #if defined(OS_MACOSX)
   // On Mac, access keys use ctrl+alt modifiers.
   static const KeyEventTestData kTestAccessA = {
     ui::VKEY_A, true, false, true, false,
     false, false, false, false, 6,
     { "D 17 0 true false false false",
       "D 18 0 true false true false",
@@ skipping 337 matching lines @@
   EXPECT_NO_FATAL_FAILURE(TestKeyEvent(tab_index, kTestAltKeySuppress));
   ASSERT_TRUE(IsViewFocused(VIEW_ID_TAB_CONTAINER));
 
   // Ctrl+Alt should have no effect.
   EXPECT_NO_FATAL_FAILURE(TestKeyEvent(tab_index, kTestCtrlAltKey));
   ASSERT_TRUE(IsViewFocused(VIEW_ID_TAB_CONTAINER));
 }
 #endif
 
 }  // namespace