linux: expose the ProcessSingleton timeout to speed tests

chrome/browser/process_singleton_linux_uitest.cc

 // Copyright (c) 2009 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "chrome/browser/process_singleton.h"
 
 #include <sys/types.h>
 #include <sys/wait.h>
 #include <signal.h>
 #include <unistd.h>
@@ skipping 40 matching lines @@
     std::vector<std::string> argv;
     argv.push_back(old_argv_[0]);
     argv.push_back(url);
     argv.push_back("--" + WideToASCII(switches::kNoProcessSingletonDialog));
 
     CommandLine::Reset();
     CommandLine::Init(argv);
 
     ProcessSingleton process_singleton(user_data_dir);
 
-    return process_singleton.NotifyOtherProcess();
+    // Use a short timeout to keep tests fast.
+    const int kTimeoutSeconds = 1;

[Paweł Hajdan Jr., 2009/09/17 19:45:56]

I'd be a bit more conservative and put 3 instead of 1 here.

Where we get to a point when even that is too slow, that's good. But for now all
50 slowest tests have run time over 5 seconds.

+    return process_singleton.NotifyOtherProcessWithTimeout(kTimeoutSeconds);
   }
 
   std::vector<std::string> old_argv_;
 };
 
 // Test if the socket file and symbol link created by ProcessSingletonLinux
 // are valid. When running this test, the ProcessSingleton object is already
 // initiated by UITest. So we just test against this existing object.
 TEST_F(ProcessSingletonLinuxTest, CheckSocketFile) {
   FilePath user_data_dir;
@@ skipping 75 matching lines @@
   // Wait for a while to make sure the browser process is actually killed.
   EXPECT_FALSE(CrashAwareSleep(1000));
 
   FilePath lock_path = user_data_dir().Append(chrome::kSingletonLockFilename);
   EXPECT_EQ(0, unlink(lock_path.value().c_str()));
   EXPECT_EQ(0, symlink("FAKEFOOHOST-1234", lock_path.value().c_str()));
 
   std::string url("about:blank");
   EXPECT_EQ(ProcessSingleton::PROFILE_IN_USE, NotifyOtherProcess(url));
 }