chromeos2-row3-rack10-host5 broken |
|||||
Issue descriptionhttps://uberchromegw.corp.google.com/i/chromeos/builders/lumpy-chrome-pfq/builds/8489 https://uberchromegw.corp.google.com/i/chromeos/builders/lumpy-chrome-pfq/builds/8490 https://uberchromegw.corp.google.com/i/chromeos/builders/lumpy-chrome-pfq/builds/8491 All 3 failures are provision failures on chromeos2-row3-rack10-host5 This DUT is blocking the PFQ at the moment.
,
Apr 5 2016
I've locked the dut: http://cautotest/afe/#tab_id=view_host&object_id=2936 xixuan, Please do following: 1. move a working dut from suites pool to bvt pool using balance_pool script 2. take a look at the failures, if they are likely hardware issue, file a bug to syslab to have it replaced (go/cros-lab-device-repair)
,
Apr 5 2016
,
Apr 5 2016
It has been removed. Current lumpy host list: ~$ dut-status -b lumpy -p bvt -g chromeos2-row3-rack10-host1 chromeos2-row3-rack10-host4 chromeos2-row3-rack9-host8 chromeos2-row3-rack9-host9 chromeos2-row3-rack9-host11 chromeos2-row3-rack9-host12 chromeos2-row3-rack9-host14 chromeos2-row3-rack9-host13 chromeos2-row3-rack9-host16 chromeos2-row3-rack9-host17 Looking at the failures now.
,
Apr 5 2016
Seems like this dut (http://cautotest/afe/#tab_id=view_host&object_id=1220) fails to update R51-8152~R51-8154 due to 'cannot boot the dut after updating'. Finally, it successfully finishes the latest provision task, and update its version to R51-8155.0.0. It's back. log: https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/59061713-chromeos-test/chromeos2-row3-rack10-host5/debug/
,
Apr 6 2016
Assume this is fixed? Please reopen if there's anything more to be done here
,
Apr 11 2016
,
May 23 2016
Bulk verified |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by achuith@chromium.org
, Apr 5 2016Owner: xixuan@chromium.org
Status: Assigned (was: Untriaged)