metadata.json does not contain reef model for reef release builds |
|||
Issue descriptionOriginally: http://b/110954989 When building reef-release, cbuildbot runs hwtests against reef DUTs, but only emits the following models in metadata.json. GE only looks at metadata.json to discover the models the build covers. So, from build: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8940670587173267792 metadata.json contains: "models" : { "basking" : { "firmware-key-id" : null, "ec-firmware-version" : "reef_v1.1.5944-8f9b570", "main-readwrite-firmware-version" : "Google_Reef.9042.178.0", "main-readonly-firmware-version" : "Google_Reef.9042.178.0" }, "electro" : { "main-readwrite-firmware-version" : "Google_Reef.9042.178.0", "main-readonly-firmware-version" : "Google_Reef.9042.178.0", "firmware-key-id" : null, "ec-firmware-version" : "reef_v1.1.5944-8f9b570" } }, The model "reef" was also expected. This appears to be true for multiple recent release branches.
,
Jul 18
From abutzier: That's the relevant data. That's why we're not showing the reef model in the build view. I don't know if that's correct or not. bhthompson@ is that wrong? From bhthompson: I am not sure, there is not 'really' a reef model at this point, but I think the only board in the lab is reef. This request came from trying to find how to get reef running tests again, today we don't seem to get any results because of the mismatches between reef the board, reef the lab construct, and electro and basking the models.
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
,
Dec 12
We will, instead, make this information available as Buildbucket tags. |
|||
►
Sign in to add a comment |
|||
Comment 1 by gmeinke@chromium.org
, Jul 18