New issue
Advanced search Search tips

Issue 636042 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Aug 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

CFM enrollment autotest timing out on oobe_exists

Project Member Reported by harpreet@chromium.org, Aug 9 2016

Issue description

Running to timeout issue on oobe_exists on various CFM devices (guado, panther, rikku, zako). Stack trace below:

08/08 04:57:43.253 WARNI|              test:0606| Autotest caught exception when running test:
Traceback (most recent call last):
  File "/usr/local/autotest/client/common_lib/test.py", line 600, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/usr/local/autotest/client/common_lib/test.py", line 804, in _call_test_function
    return func(*args, **dargs)
  File "/usr/local/autotest/client/common_lib/test.py", line 461, in execute
    dargs)
  File "/usr/local/autotest/client/common_lib/test.py", line 347, in _call_run_once_with_retry
    postprocess_profiled_run, args, dargs)
  File "/usr/local/autotest/client/common_lib/test.py", line 376, in _call_run_once
    self.run_once(*args, **dargs)
  File "/usr/local/autotest/server/site_tests/enterprise_CFM_VolumeChange/enterprise_CFM_VolumeChange.py", line 119, in run_once
    raise error.TestFail(str(e))
TestFail: RPC error: cfm.enroll_device
Traceback (most recent call last):
  File "./multimedia_xmlrpc_server.py", line 70, in _dispatch
    return func(*params)
  File "/usr/local/autotest/cros/multimedia/cfm_facade_native.py", line 39, in enroll_device
    self._resource.start_custom_chrome({"auto_login": False})
  File "/usr/local/autotest/cros/multimedia/facade_resource.py", line 57, in start_custom_chrome
    self._chrome = chrome.Chrome(**kwargs)
  File "/usr/local/autotest/common_lib/cros/chrome.py", line 189, in __init__
    self._browser = browser_to_create.Create(finder_options)
  File "/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/cros_browser_finder.py", line 50, in Create
    self._credentials_path)
  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, credentials_path)
  File "/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/browser/browser.py", line 55, in __init__
    self._browser_backend.Start()
  File "/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/cros_browser_backend.py", line 126, in Start
    util.WaitFor(lambda: self.oobe_exists, 10)
  File "/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/core/util.py", line 94, in WaitFor
    (timeout, GetConditionString()))
TimeoutException: Timed out while waiting 10s for util.WaitFor(lambda: self.oobe_exists, 10).



Change oobe_exists timeout value in cros_browser_backend.py to 30 seconds.
 
Status: Fixed (was: Started)
Project Member

Comment 2 by bugdroid1@chromium.org, Aug 10 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/0a800043dcc000eb0b73977d6933d8e528ef11ce

commit 0a800043dcc000eb0b73977d6933d8e528ef11ce
Author: catapult-deps-roller <catapult-deps-roller@chromium.org>
Date: Wed Aug 10 00:51:16 2016

Roll src/third_party/catapult/ bf4b1c0d2..280817e10 (5 commits).

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/bf4b1c0d2dcd..280817e10a2c

$ git log bf4b1c0d2..280817e10 --date=short --no-merges --format='%ad %ae %s'

BUG= 636042 

TBR=catapult-sheriff@chromium.org

Review-Url: https://codereview.chromium.org/2228173002
Cr-Commit-Position: refs/heads/master@{#410904}

[modify] https://crrev.com/0a800043dcc000eb0b73977d6933d8e528ef11ce/DEPS

Labels: VerifyIn-54

Comment 4 by dchan@chromium.org, Oct 7 2016

Labels: VerifyIn-55

Comment 5 by dchan@google.com, Nov 19 2016

Labels: VerifyIn-56

Comment 6 by dchan@google.com, Jan 21 2017

Labels: VerifyIn-57

Comment 7 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58

Comment 8 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 9 by dchan@google.com, May 30 2017

Labels: VerifyIn-60
Labels: VerifyIn-61
Status: Verified (was: Fixed)

Sign in to add a comment