From 1105c3ead05ab927e53a129691319a75a1ae1e15 Mon Sep 17 00:00:00 2001 From: "estade@chromium.org" Date: Mon, 31 Aug 2009 19:36:33 +0000 Subject: Don't hardcode the timeout in the unload ui test. The too-short timeout was making it leak in valgrind. BUG=20617 Review URL: http://codereview.chromium.org/180044 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@24919 0039d316-1c4b-4281-b951-d872f2087c98 --- chrome/browser/unload_uitest.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'chrome/browser/unload_uitest.cc') diff --git a/chrome/browser/unload_uitest.cc b/chrome/browser/unload_uitest.cc index b66cc22..8a61bcc 100644 --- a/chrome/browser/unload_uitest.cc +++ b/chrome/browser/unload_uitest.cc @@ -157,7 +157,7 @@ class UnloadTest : public UITest { #if defined(OS_WIN) || defined(OS_LINUX) bool modal_dialog_showing = false; MessageBoxFlags::DialogButton available_buttons; - EXPECT_TRUE(automation()->WaitForAppModalDialog(3000)); + EXPECT_TRUE(automation()->WaitForAppModalDialog(action_timeout_ms())); EXPECT_TRUE(automation()->GetShowingAppModalDialog(&modal_dialog_showing, &available_buttons)); ASSERT_TRUE(modal_dialog_showing); -- cgit v1.1