[ChromeDriver] Adjust DevTools connect timeout

Change the initial DevTools connect timeout from 1 second to 2 seconds.
While a timeout of 1 second was sufficient for Linux and Mac, it turned
out to be too short for Windows, where a normal successful connection
usually takes very close to 1 second.

Change-Id: I685ac9aa45a7ce250f2af718959661c59dcf8f0d
Reviewed-on: https://chromium-review.googlesource.com/1037806Reviewed-by: Jonathon Kereliuk <kereliuk@chromium.org>
Commit-Queue: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555549}

chrome/test/chromedriver/net/sync_websocket_impl.cc

@@ -55,11 +55,12 @@ bool SyncWebSocketImpl::Core::Connect(const GURL& url) {
   bool success = false;
   base::WaitableEvent event(base::WaitableEvent::ResetPolicy::AUTOMATIC,
                             base::WaitableEvent::InitialState::NOT_SIGNALED);
-  // Connect with retries. The retry timeout starts at 1 second, with
+  // Connect with retries. The retry timeout starts at 2 seconds, with
   // exponential backoff, up to 16 seconds. The maximum total wait time is
-  // about 31 seconds.
+  // about 30 seconds. (Normally, a successful connection takes only a few
+  // milliseconds on Linux and Mac, but around a second on Windows.)
   const int kMaxTimeout = 16;
-  for (int timeout = 1; timeout <= kMaxTimeout; timeout *= 2) {
+  for (int timeout = 2; timeout <= kMaxTimeout; timeout *= 2) {
     context_getter_->GetNetworkTaskRunner()->PostTask(
         FROM_HERE, base::BindOnce(&SyncWebSocketImpl::Core::ConnectOnIO, this,
                                   url, &success, &event));