[chromedriver] Apply page load timeout to slow cross-process navigations

chrome/test/chromedriver/util.cc

 // Copyright (c) 2013 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/test/chromedriver/util.h"
 
 #include <stddef.h>
 #include <stdint.h>
 
 #include "base/base64.h"
@@ skipping 11 matching lines @@
 #include "chrome/test/chromedriver/chrome/browser_info.h"
 #include "chrome/test/chromedriver/chrome/chrome.h"
 #include "chrome/test/chromedriver/chrome/status.h"
 #include "chrome/test/chromedriver/chrome/ui_events.h"
 #include "chrome/test/chromedriver/chrome/web_view.h"
 #include "chrome/test/chromedriver/command_listener.h"
 #include "chrome/test/chromedriver/key_converter.h"
 #include "chrome/test/chromedriver/session.h"
 #include "third_party/zlib/google/zip.h"
 
+Timeout::Timeout() : start_(base::TimeTicks::Now()) {
+}
+
+Timeout::Timeout(const base::TimeDelta& duration) : Timeout() {
+  SetDuration(duration);
+}
+
+Timeout::Timeout(const base::TimeDelta& duration, const Timeout* outer)
+    : Timeout(duration) {
+  if (outer && !outer->deadline_.is_null())
+    deadline_ = std::min(outer->deadline_, deadline_);
+}
+
+void Timeout::SetDuration(const base::TimeDelta& duration) {
+  DCHECK(!start_.is_null());
+  DCHECK(deadline_.is_null());

[samuong, 2016/02/19 20:18:57]

ChromeDriver is a bit different from Chrome in that 1) we don't get crash
reports from users and 2) few (if any) people use debug builds, so these checks
will never get run. This makes DCHECK() less useful here, and anyway this will
only get called once per instance, so I think we should change this to an if
condition, and log the error.

[Alexander Semashko, 2016/02/19 23:38:58]

Yeah, I put DCHECKs here hoping they'll be hit in tests if something violates
the conditions. But I don't know if Chromedriver integration tests are run with
debug builds or DCHECK_ALWAYS_ON. Do they? Probably it would be best to keep
DCHECKs and add logs?

[samuong, 2016/02/20 00:11:44]

For the C++ unit tests, they'll get built differently depending on which bot is
doing the building. Some will get built in Debug mode, with DCHECKs enabled. But
ChromeDriver gets built with target=Release in the end-to-end tests, here's an
example:

https://build.chromium.org/p/chromium.chromedriver/builders/Linux/builds/1685...

In these tests, if something goes wrong, it'll crash chromedriver and I suspect
it'd be pretty hard to figure out what happened, so adding logs would definitely
help there.

[Alexander Semashko, 2016/02/24 12:51:20]

Done.

+  deadline_ = start_ + duration;
+}
+
+bool Timeout::IsExpired() const {
+  return GetRemainingTime() <= base::TimeDelta();
+}
+
+base::TimeDelta Timeout::GetDuration() const {
+  return !deadline_.is_null() ? deadline_ - start_
+                              : base::TimeDelta::Max();
+}
+
+base::TimeDelta Timeout::GetRemainingTime() const {
+  return !deadline_.is_null() ? deadline_ - base::TimeTicks::Now()
+                              : base::TimeDelta::Max();
+}
+
 std::string GenerateId() {
   uint64_t msb = base::RandUint64();
   uint64_t lsb = base::RandUint64();
   return base::StringPrintf("%016" PRIx64 "%016" PRIx64, msb, lsb);
 }
 
 namespace {
 
 Status FlattenStringArray(const base::ListValue* src, base::string16* dest) {
   base::string16 keys;
@@ skipping 385 matching lines @@
       if (session->chrome) {
         const BrowserInfo* browser_info = session->chrome->GetBrowserInfo();
         status.AddDetails("Session info: " + browser_info->browser_name + "=" +
                           browser_info->browser_version);
       }
       return status;
     }
   }
   return Status(kOk);
 }