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

Issue 623788 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

Testbed board labels different than single device

Project Member Reported by sbasi@chromium.org, Jun 28 2016

Issue description

If I create a testbed of 2 devices I get labels of board:dragonboard-1 & board:dragonboard-2

But if I create a single device host I get label board:brillo-dragonboard .

Kevin is there a reason behind this difference?


Looking at cautotest I see board:android-angler-2 and board:angler-2 meaning we have some inconsistencies and cleanup we need to do.
 
The difference is between an ADBHost and TestBed.  ADBHost will create a board label with no #, TestBed will append numbers to the board labels.

As for the inconsistencies, once I get a label verifier for ADBHost in, it should automatically clean up hosts for us.

Comment 2 by sbasi@chromium.org, Jun 28 2016

Yeah the number part was expected, the missing prefix was not. But according to your suite support doc the prefix change was expected.

As for the clean up, we need to schedule that carefully because we need to adjust our ATP configs to use the new board name correct?
Oh whoops, totally missed that difference, the prefix shouldn't be there, are you looking at a label generated a while back?  crosreview.com/342483 removed the os from the board label to help with the testbed suite changes.

We can do the clean up today since we don't need to depend on the verifier.  It's just a matter of updating the existing labels to remove the os from it and updating the ATP configs at the same time.  I'll send out a cl to update the ATP configs right now.
Brillo devices have been updated, next will be android devices
Status: Assigned (was: Untriaged)

Sign in to add a comment