New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 1 user

Issue metadata

Status: Fixed
Last visit > 30 days ago
Closed: Mar 2018
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Sign in to add a comment

Issue 810247: wolf-paladin fails: Start browser timeout

Reported by, Feb 8 2018 Project Member

Issue description

Several tests (login_LogoutProcessCleanup, login_CryptohomeIncognito, security_SandboxStatus, etc) failed on wolf-paladin due to the following timeout:

02/07 19:58:01.494 ERROR|           browser:0055| Failed with TimeoutException while starting the browser backend.
02/07 19:58:02.097 WARNI|              test:0637| The test failed with the following exception
Traceback (most recent call last):
  File "/usr/local/autotest/common_lib/", line 631, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/usr/local/autotest/common_lib/", line 837, in _call_test_function
    raise error.UnhandledTestFail(e)
UnhandledTestFail: Unhandled TimeoutException: Timed out while waiting 15s for py_utils.WaitFor(lambda: pid !=, 15).
Traceback (most recent call last):
  File "/usr/local/autotest/common_lib/", line 831, in _call_test_function
    return func(*args, **dargs)
  File "/usr/local/autotest/common_lib/", line 495, in execute
  File "/usr/local/autotest/common_lib/", line 362, in _call_run_once_with_retry
    postprocess_profiled_run, args, dargs)
  File "/usr/local/autotest/common_lib/", line 400, in _call_run_once
    self.run_once(*args, **dargs)
  File "/usr/local/autotest/tests/login_LogoutProcessCleanup/", line 130, in run_once
    with chrome.Chrome() as cr:
  File "/usr/local/autotest/common_lib/cros/", line 173, in __init__
    self._browser = self._browser_to_create.Create()
  File "/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/", line 58, in Create
    browser_backend, self._platform_backend, startup_args)
  File "/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/", line 14, in __init__
    backend, platform_backend, startup_args)
  File "/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/browser/", line 47, in __init__
    self._browser_backend.Start(startup_args, startup_url=startup_url)
  File "/usr/local/telemetry/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/", line 52, in traced_function
    return func(*args, **kwargs)
  File "/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/", line 153, in Start
    py_utils.WaitFor(lambda: pid !=, 15)
  File "/usr/local/telemetry/src/third_party/catapult/common/py_utils/py_utils/", line 148, in WaitFor
    (timeout, GetConditionString()))
TimeoutException: Timed out while waiting 15s for py_utils.WaitFor(lambda: pid !=, 15).

It happened 2 times in a row (12692, 12693).
Not sure if it is a infra issue?

Comment 1 by, Feb 8 2018


Comment 2 by, Feb 8 2018

Owner: ----
Can you offer a failed wolf-paladin link?

Comment 4 by, Feb 9 2018

It's experimental, so I assume it's not well supported.

This should be caused by a bug in ToT. Due to it's experimental board, I'm not sure whether it's high priority to investigate it. Let sheriff decide & find an owner.

Comment 5 by, Mar 30 2018

Status: Fixed (was: Assigned)

Sign in to add a comment