Issue metadata
Sign in to add a comment
|
chromeos4-row11-rack10-host13 stuck in a repair loop |
||||||||||||||||||||||||
Issue descriptionIn this builder, several tests failed. All of them happened to land on chromeos4-row11-rack10-host13 and all of them timed out during provisioning: https://luci-milo.appspot.com/buildbot/chromeos/cyan-nyc-android-pfq/1504 dut-status shows the board doing a series of provision/repair operations without any intervening tests.
,
Jan 26 2018
This looping DUT was detected by this morning's regular pool inventory scan: 2018-01-26 06:45:27 | INFO | Looping DUT: chromeos4-row11-rack10-host13, board: cyan, pool: bvt
,
Jan 26 2018
,
Jan 26 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by jkop@chromium.org
, Jan 26 2018Status: Assigned (was: Untriaged)
Summary: chromeos4-row11-rack10-host13 stuck in a repair loop (was: chromeos4-row11-rack10-host13 is failing to provision)