summaryrefslogtreecommitdiffstats
path: root/chrome/browser/cocoa/browser_window_controller_unittest.mm
diff options
context:
space:
mode:
Diffstat (limited to 'chrome/browser/cocoa/browser_window_controller_unittest.mm')
-rw-r--r--chrome/browser/cocoa/browser_window_controller_unittest.mm7
1 files changed, 5 insertions, 2 deletions
diff --git a/chrome/browser/cocoa/browser_window_controller_unittest.mm b/chrome/browser/cocoa/browser_window_controller_unittest.mm
index 01ceff0..0a56165 100644
--- a/chrome/browser/cocoa/browser_window_controller_unittest.mm
+++ b/chrome/browser/cocoa/browser_window_controller_unittest.mm
@@ -587,8 +587,11 @@ TEST_F(BrowserWindowFullScreenControllerTest, TestFullscreen) {
EXPECT_FALSE([controller_ isFullscreen]);
}
-// Failing on Chromium Mac: http://crbug/53586
-TEST_F(BrowserWindowFullScreenControllerTest, FLAKY_TestActivate) {
+// If this test fails, it is usually a sign that the bots have some sort of
+// problem (such as a modal dialog up). This tests is a very useful canary, so
+// please do not mark it as flaky without first verifying that there are no bot
+// problems.
+TEST_F(BrowserWindowFullScreenControllerTest, TestActivate) {
EXPECT_FALSE([controller_ isFullscreen]);
[controller_ activate];