one unresponsive DUT caused CQ to fail |
||
Issue descriptionWhen attempting to provision chromeos4-row13-rack1-host12 for a HWTest (bvt-cq), the DUT did not respond. (It still won't ping now.) This apparently caused failure of the entire CQ run. Do we/should we try again on a different DUT before giving up? https://uberchromegw.corp.google.com/i/chromeos/builders/nyan_kitty-paladin/builds/400 https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/95326402-chromeos-test/chromeos4-row13-rack1-host12/debug/
,
Jan 11 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by autumn@chromium.org
, Jan 11 2017