Disabling ChromeFrame.Launch

chrome_frame/test/chrome_frame_automation_mock.cc

Index: chrome_frame/test/chrome_frame_automation_mock.cc
diff --git a/chrome_frame/test/chrome_frame_automation_mock.cc b/chrome_frame/test/chrome_frame_automation_mock.cc
index 1f50b2efb8a2558fe3cb8c90937c60d2ac5cf681..fae0ae1a8903bc4e6da1ebe56c8c3225636d1eb6 100644
--- a/chrome_frame/test/chrome_frame_automation_mock.cc
+++ b/chrome_frame/test/chrome_frame_automation_mock.cc
@@ -8,7 +8,10 @@
 
 const int kLongWaitTimeout = 25 * 1000;
 
-TEST(ChromeFrame, Launch) {
+// Note that this test fails occasionally. Disabling it altogether (rather than
+// marking as flaky to see if the failure cascades down to the next test.
+// http://crbug.com/81479
+TEST(ChromeFrame, DISABLED_Launch) {
   MessageLoopForUI loop;
   AutomationMockLaunch mock_launch(&loop, kLongWaitTimeout);