summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-03-26 21:42:20 +0000
committerananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-03-26 21:42:20 +0000
commit90ef2e048af8572f9b8dbac6d8385b7c70bb80b7 (patch)
tree4a193f704e5b7b15e1407fcd242772c40b461f7c
parentdc0412127385b73df3647ebfb313b61e51ef1496 (diff)
downloadchromium_src-90ef2e048af8572f9b8dbac6d8385b7c70bb80b7.zip
chromium_src-90ef2e048af8572f9b8dbac6d8385b7c70bb80b7.tar.gz
chromium_src-90ef2e048af8572f9b8dbac6d8385b7c70bb80b7.tar.bz2
Marking the CrossSiteInfiniteBeforeUnloadAsync test as flaky as it fails randomly on the valgrind
Linux builder. It appears that this was already marked flaky in revision 42358. I synced to head and still can't get that change. Bug=39057 TBR=amit Review URL: http://codereview.chromium.org/1468002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42826 0039d316-1c4b-4281-b951-d872f2087c98
-rw-r--r--chrome/browser/unload_uitest.cc3
1 files changed, 2 insertions, 1 deletions
diff --git a/chrome/browser/unload_uitest.cc b/chrome/browser/unload_uitest.cc
index d209b2a..5ee30b7 100644
--- a/chrome/browser/unload_uitest.cc
+++ b/chrome/browser/unload_uitest.cc
@@ -250,7 +250,8 @@ TEST_F(UnloadTest, DISABLED_CrossSiteInfiniteUnloadAsyncInputEvent) {
// Navigate to a page with an infinite beforeunload handler.
// Then two two async crosssite requests to ensure
// we don't get confused and think we're closing the tab.
-TEST_F(UnloadTest, CrossSiteInfiniteBeforeUnloadAsync) {
+// This test is flaky on the valgrind UI bots. http://crbug.com/39057
+TEST_F(UnloadTest, FLAKY_CrossSiteInfiniteBeforeUnloadAsync) {
// Tests makes no sense in single-process mode since the renderer is hung.
if (CommandLine::ForCurrentProcess()->HasSwitch(switches::kSingleProcess))
return;