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

Issue 857604 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Jul 25
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Scarlet boards in the lab have model:scarlet but are really model:dru

Project Member Reported by bhthompson@google.com, Jun 28 2018

Issue description

We don't seem to have a scarlet model, we only have a dru model in the scarlet board, but querying the lab it looks like we have a bunch of model:scarlet that should be invalid, and no model:dru.

bhthompson@ragnarok:/usr/local/ssd960gb/chromiumos-1/src/third_party/autotest/files/contrib$ atest host list -b model:dru | ./count_labels -p
bhthompson@ragnarok:/usr/local/ssd960gb/chromiumos-1/src/third_party/autotest/files/contrib$ atest host list -b model:scarlet | ./count_labels -p 
     10 bvt
      1 crosperf
      6 cts
      1 faft-cr50
      3 faft-test
      8 suites
      1 wificell
bhthompson@ragnarok:/usr/local/ssd960gb/chromiumos-1/src/third_party/autotest/files/contrib$

Should we relabel the model:scarlet systems to model:dru?

FWIW lab board name in https://cros-goldeneye.corp.google.com/chromeos/console/viewModel?name=dru may not be working, we should probably clear this when we get our model labels right.
 
Cc: englab-sys-cros@google.com
How are the model names determined?  I figured it via HWID so SCARLET B5B-A2D-D2K-D6O
Mergedinto: 867624
Status: Duplicate (was: Untriaged)

Sign in to add a comment