teemo (fizz) stuck in repair loop |
|||
Issue descriptionlooks like teemo is stuck in repair loop, the result is that our build test report for M67 is more red https://viceroy.corp.google.com/chromeos/repair_loops Looks like all of our 5 bvt teemo are in repair loop shows DUT name Model Pool chromeos4-row10-rack1-host15 teemo bvt chromeos4-row10-rack1-host16 teemo bvt chromeos4-row10-rack1-host17 teemo bvt chromeos4-row10-rack1-host21 teemo bvt chromeos4-row10-rack2-host1 teemo bvt chromeos4-row11-rack7-host5 reks bvt chromeos2-row8-rack1-host18 whitetip suites chromeos6-row4-rack17-host7 eve suites +kalin as FYI on the suites device (they are own and operated by test team)
,
Mar 29 2018
,
Mar 29 2018
Most of them are in Ready status, and manually kicked off verify job also finished without issues.
,
Apr 2 2018
,
Apr 2 2018
is viceroy data stale ? The page currently still list teemo, should they also have timestamp ? |
|||
►
Sign in to add a comment |
|||
Comment 1 by dchan@chromium.org
, Mar 29 2018