New issue
Advanced search Search tips

Issue 796432 link

Starred by 1 user
Status: Duplicate
Merged: issue 789077
Owner: ----
Closed: Dec 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

veyron_minnie-paladin:4808 failed

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Dec 20 2017 
Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of bmgordon@google.com

veyron_minnie-paladin:4808 failed

Builders failed on: 
- veyron_minnie-paladin: 
  https://luci-milo.appspot.com/buildbot/chromeos/veyron_minnie-paladin/4808

The provision stage shows a bunch of errors in the logs that look like this:
Servo initialize timed out., Unhandled DevServerException: CrOS auto-update failed for host chromeos4-row9-rack11-host12: 0) RootfsUpdateError: Failed to perform rootfs update: SSHConnectionError('ssh: Could not resolve hostname chromeos4-row9-rack11-host12: Name or service not known\r\n',), 1) RootfsUpdateError: Failed to perform rootfs update: RootfsUpdateError('Update failed with unexpected update status: UPDATE_STATUS_IDLE',), 
12/19 15:02:17.272 ERROR|   logging_manager:0626| tko parser: parsing test ---- SERVER_JOB

That stage is marked success, but then the following bvt-arc stage times out.

Comment 1 by jrbarnette@chromium.org, Dec 20 2017

Mergedinto: 789077
Status: Duplicate (was: Available)
The problem was that the provision failure left the CQ pool down
one DUT.  That made the suite run slower, so that it timed out.

The provision failure itself was bug 789077; we don't have a handle
yet on what causes that.  :-(
►

Sign in to add a comment