Increase maximum sleep time.

From experience of measuring the time to succeed on our bots, 1 in 10000 times
the start time came up as high as 25 seconds.  This bumps the theoretical
sleep time over that threshhold.

Also updated the title comment description, since this changes the numbers,
and the rest was not updated as the purpose expanded.

R=sadrul@chromium.org
BUG=103882
TEST=try jobs.

Review URL: http://codereview.chromium.org/10008101

Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 62386cb469717905ec38284a8079b21678e57b01
diff --git a/xdisplaycheck.cc b/xdisplaycheck.cc
index ba4f26f..6c4c677 100644
--- a/xdisplaycheck.cc
+++ b/xdisplaycheck.cc
@@ -3,11 +3,11 @@
 // found in the LICENSE file.
 //
 // This is a small program that tries to connect to the X server.  It
-// continually retries until it connects or 5 seconds pass.  If it fails
-// to connect to the X server after 5 seconds, it returns an error code
-// of -1.
+// continually retries until it connects or 30 seconds pass.  If it fails
+// to connect to the X server or fails to find needed functiona, it returns
+// an error code of -1.
 //
-// This is to help verify that the X server is available before we start
+// This is to help verify that a useful X server is available before we start
 // start running tests on the build bots.
 
 #include <errno.h>
@@ -34,7 +34,7 @@
 }
 
 int main(int argc, char* argv[]) {
-  int kNumTries = 50;  // 49*48/2 * 10 = 12.25s of waiting
+  int kNumTries = 78;  // 78*77/2 * 10 = 30s of waiting
   Display* display = NULL;
   int tries;
   for (tries = 0; tries < kNumTries; ++tries) {