linux: expose the ProcessSingleton timeout to speed tests

chrome/browser/process_singleton_linux_uitest.cc

Index: chrome/browser/process_singleton_linux_uitest.cc
diff --git a/chrome/browser/process_singleton_linux_uitest.cc b/chrome/browser/process_singleton_linux_uitest.cc
index 6119e3d8a5402c9ff83aaeae081f4b4c953a611a..d85f0ebf706017de154d5336c1d835ea5cab5dae 100644
--- a/chrome/browser/process_singleton_linux_uitest.cc
+++ b/chrome/browser/process_singleton_linux_uitest.cc
@@ -58,7 +58,9 @@ class ProcessSingletonLinuxTest : public UITest {
 
     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_;