Disable single-process mode in ExtensionViewTest, to see if it's causing

buildbot problems.
Review URL: http://codereview.chromium.org/46052

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@11662 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 3 insertions, 3 deletions

diff --git a/chrome/browser/extensions/extension_view_unittest.cc b/chrome/browser/extensions/extension_view_unittest.cc
index 4003954..b446920 100755
--- a/chrome/browser/extensions/extension_view_unittest.cc
+++ b/chrome/browser/extensions/extension_view_unittest.cc
@@ -18,10 +18,10 @@ namespace {
 
 // How long to wait for the extension to put up a javascript alert before giving
 // up.
-const int kAlertTimeoutMs = 10000;
+const int kAlertTimeoutMs = 20000;
 
 // How long to wait for the extension to load before giving up.
-const int kLoadTimeoutMs = 5000;
+const int kLoadTimeoutMs = 10000;
 
 // The extension we're using as our test case.
 const char* kExtensionId = "00123456789abcdef0123456789abcdef0123456";
@@ -105,7 +105,7 @@ class ExtensionViewTest : public InProcessBrowserTest {
     ExtensionErrorReporter::Init(false);
 
     // Use single-process in an attempt to speed it up and make it less flaky.
-    EnableSingleProcess();
+    //EnableSingleProcess();
 
     InProcessBrowserTest::SetUp();
   }