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

Issue 785562 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

cros_browser_backend.py timed-out while calling IsCryptohomeMounted()

Project Member Reported by laszio@chromium.org, Nov 16 2017

Issue description

This is intermittent but happens frequently on two lumpy DUTs (see below) this week. I only observed the failures on these 2 lumpy devices but not other boards. It looks like that these 2 lumpy devices may need to be replaced.

On the other hand, do we need lumpy? They are pretty old (sandybridge) and we have peppy (haswell) for Intel "big" cores.

chromeos2-row9-rack9-host9.cros
chromeos2-row9-rack9-host11.cros

Traceback (most recent call last):
  RunBenchmark at /tmp/chrome_root/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py:339
    max_num_values=benchmark.MAX_NUM_VALUES)
  Run at /tmp/chrome_root/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py:252
    state.TearDownState()
  traced_function at /tmp/chrome_root/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py:52
    return func(*args, **kwargs)
  TearDownState at /tmp/chrome_root/src/third_party/catapult/telemetry/telemetry/page/shared_page_state.py:337
    self._StopBrowser()
  traced_function at /tmp/chrome_root/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py:52
    return func(*args, **kwargs)
  _StopBrowser at /tmp/chrome_root/src/third_party/catapult/telemetry/telemetry/page/shared_page_state.py:343
    self._browser.Close()
  Close at /tmp/chrome_root/src/third_party/catapult/telemetry/telemetry/internal/browser/browser.py:278
    self._browser_backend.Close()
  traced_function at /tmp/chrome_root/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py:52
    return func(*args, **kwargs)
  Close at /tmp/chrome_root/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/cros_browser_backend.py:214
    py_utils.WaitFor(lambda: not self._IsCryptohomeMounted(), 180)
  WaitFor at /tmp/chrome_root/src/third_party/catapult/common/py_utils/py_utils/__init__.py:148
    (timeout, GetConditionString()))
TimeoutException: Timed out while waiting 180s for py_utils.WaitFor(lambda: not self._IsCryptohomeMounted(), 180).

 

Comment 1 by vapier@chromium.org, Nov 16 2017

I'd recommend migrating everything off of lumpy. its eol is coming up in the next year. might as well get ahead of it now.

Comment 2 by laszio@chromium.org, Nov 17 2017

Just talked with Caroline and we have one spare machine that is online. So let's try to replace one of the machines and make sure it is a hardware problem.

Comment 3 by laszio@chromium.org, Nov 17 2017

The failures happened evenly (32 times v.s. 34) on both of the machines. I strongly doubt that this is a hardware issue...

Comment 4 by laszio@chromium.org, Nov 17 2017

Cc: achuith@chromium.org nednguyen@chromium.org

Comment 5 by cmt...@chromium.org, Nov 17 2017

Is there any chance the failures you are seeing could be related to this: https://bugs.chromium.org/p/chromium/issues/detail?id=774036
It does seem that there's either a lumpy-specific issue at play here, or more likely something wrong with the particular DUTs in the lab.

Sign in to add a comment