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

Issue 911766 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocking:
issue 913145



Sign in to add a comment

power_LoadTest.1hour fail on nocturne - moblab

Reported by chasing....@gmail.com, Dec 4

Issue description

Test: power_LoadTest.1hour
Job tag: 7-moblab/192.168.231.100
Job name: plt1hr
Status: FAIL
Reason: Unhandled TimeoutException: Timed out while waiting 60s for py_utils.WaitFor(lambda: not self._GaiaWebviewContext(), 60).
Test started: 2018-12-03 18:30:35
Test finished: 2018-12-03 18:32:01
Host: 192.168.231.100
Platform: nocturne
Kernel: 4.4.165-15537-g77480abc681f
Test labels: none

bug submitted from mqg@ moblab test account
 
7-moblab.tar.xz
215 KB Download
Cc: haddowk@chromium.org mqg@chromium.org tbroch@chromium.org puthik@google.com
Owner: mattmallett@chromium.org
Is this an issue with the test/device stability or with moblab? In general, once the test has provisioned and started successfully, the moblab autotest environment is identical to to lab autotest environment.
Blocking: 913145
Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Sign in to add a comment