[coral] test suite configuration does not behave as expected on some coral boards |
||||
Issue descriptionAs the suite configuration listed in - https://cros-goldeneye.corp.google.com/chromeos/console/listModel, we know that we enable sanity tests for robo, robo360, nasher and nasher360 models. However, from the coral buildbot, all robo360 and nasher360 test suites are still skipped. e.g. robo360 sanity test - https://logs.chromium.org/v/?s=chromeos%2Fbb%2Fchromeos%2Fcoral-release%2F594%2F%2B%2Frecipes%2Fsteps%2FHWTest__sanity___robo360_%2F0%2Fstdout nasher360 sanity test - https://logs.chromium.org/v/?s=chromeos%2Fbb%2Fchromeos%2Fcoral-release%2F594%2F%2B%2Frecipes%2Fsteps%2FHWTest__sanity___nasher360_%2F0%2Fstdout Same as bvt-inline tests: https://logs.chromium.org/v/?s=chromeos%2Fbb%2Fchromeos%2Fcoral-release%2F594%2F%2B%2Frecipes%2Fsteps%2FHWTest__bvt-inline___nasher360_%2F0%2Fstdout
,
Dec 13 2017
this is still related to lab provisioning ... to ppichia@
,
Dec 14 2017
,
Dec 15 2017
Should be fine now
atest host list -b board:coral | grep pool:bvt | awk '{ print $6 }' | sort | uniq
astronaut
nasher
nasher360
robo
robo360
santa
,
Jul 24
|
||||
►
Sign in to add a comment |
||||
Comment 1 by cywang@chromium.org
, Dec 13 2017