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

Issue 612494 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 605623
Owner: ----
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

test ran on two drones

Project Member Reported by kevcheng@chromium.org, May 17 2016

Issue description

From: https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/63592576-chromeos-test/brillo-row1-legorack3-b1e12318/debug

This test was scheduled to run on these 2 drones:
- test_63592576_1463497424_11094
- cros-autotest-shard5.hot.corp.google.com

Is that expected? It looked like two autoserv processes were kicked off for this same test and caused the host initialization to be all wonky (and failed).  Is test_63592576_1463497424_11094 even a valid drone? That doesn't seem to resolve to anything.
 

Comment 1 by dshi@chromium.org, May 17 2016

The first one, test_63592576_1463497424_11094, is a container running inside the actual drone. It's set up by server side packaging.
Cc: -fdeng@chromium.org -shuqianz@chromium.org -xixuan@chromium.org sbasi@chromium.org
ahh... ok, in that case is there something going on with SSP? It looks like we run the test in the container before the actual drone, is that right?  And the drone run doesn't seem to get the host attributes properly either since the test failed because no serial was passed in (the drone does have the serial in the host attributes though) and was running adb commands without a serial specified.
Mergedinto: 605623
Status: Duplicate (was: Untriaged)
Dan explained to me the second autoserv run was actually crash_collection and that's failing for a reason already known. Duping into existing bug.

Sign in to add a comment