New issue
Advanced search Search tips

Issue 907162 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Result show tests executed on non-existing coral model

Project Member Reported by dchan@google.com, Nov 20

Issue description


https://stainless.corp.google.com/search?view=matrix&row=suite&col=board_model&first_date=2018-11-18&last_date=2018-11-20&suite=%5Epaygen_%7C%5Ebvt&board=%5Ecoral%24&exclude_cts=false&exclude_not_run=false&exclude_non_release=true&exclude_au=false&exclude_acts=true&exclude_retried=true&exclude_non_production=false

screen shot: https://screenshot.googleplex.com/uyw4XGmPzoc.png



Issue with what's showing above:
1- there is no coral board and coral model but stainless is showing result.  Run atest host list -b model:coral returns nothing

2- we have 17 suites for robo model and no BVT unis.

3- the test executed for coral/coral is in fact robo. (click on any test run for coral/coral, locate the hostname and check against atest, you will find that model:robo board:coral (or ssh to the dut and run crossystem  hwid



 
This only affects coral-tast-cq it looks like?
Owner: ayatane@chromium.org
Status: Assigned (was: Untriaged)
I don't know the importance or urgency of this issue.  If it only affects bvt-tast-cq, it may be some issue in how Tast results get parsed, possibly related to parsing changes added for Skylab (although said changes should not affect Autotest tests).

Sign in to add a comment