New issue
Advanced search Search tips
Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Mar 30
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

wolf-paladin fails: Start browser timeout

Project Member Reported by shenghao@chromium.org, Feb 8

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/test.py", line 631, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/usr/local/autotest/common_lib/test.py", line 837, in _call_test_function
    raise error.UnhandledTestFail(e)
UnhandledTestFail: Unhandled TimeoutException: Timed out while waiting 15s for py_utils.WaitFor(lambda: pid != self.pid, 15).
Traceback (most recent call last):
  File "/usr/local/autotest/common_lib/test.py", line 831, in _call_test_function
    return func(*args, **dargs)
  File "/usr/local/autotest/common_lib/test.py", line 495, in execute
    dargs)
  File "/usr/local/autotest/common_lib/test.py", line 362, in _call_run_once_with_retry
    postprocess_profiled_run, args, dargs)
  File "/usr/local/autotest/common_lib/test.py", line 400, in _call_run_once
    self.run_once(*args, **dargs)
  File "/usr/local/autotest/tests/login_LogoutProcessCleanup/login_LogoutProcessCleanup.py", line 130, in run_once
    with chrome.Chrome() as cr:
  File "/usr/local/autotest/common_lib/cros/chrome.py", line 173, in __init__
    self._browser = self._browser_to_create.Create()
  File "/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/cros_browser_finder.py", line 58, in Create
    browser_backend, self._platform_backend, startup_args)
  File "/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/cros_browser_with_oobe.py", line 14, in __init__
    backend, platform_backend, startup_args)
  File "/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/browser/browser.py", 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/decorators.py", line 52, in traced_function
    return func(*args, **kwargs)
  File "/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/cros_browser_backend.py", line 153, in Start
    py_utils.WaitFor(lambda: pid != self.pid, 15)
  File "/usr/local/telemetry/src/third_party/catapult/common/py_utils/py_utils/__init__.py", line 148, in WaitFor
    (timeout, GetConditionString()))
TimeoutException: Timed out while waiting 15s for py_utils.WaitFor(lambda: pid != self.pid, 15).


It happened 2 times in a row (12692, 12693).
Not sure if it is a infra issue?
 
Cc: shenghao@chromium.org
Cc: xixuan@chromium.org
Owner: ----
Can you offer a failed wolf-paladin link?
Owner: cra...@chromium.org
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.
Status: Fixed (was: Assigned)

Sign in to add a comment