daisy BVT pool needs repair |
|||||||||||||||
Issue descriptionSee autofiled Issue 597917. Latest canary failure: https://uberchromegw.corp.google.com/i/chromeos/builders/daisy-release-group/builds/4838 The number of available DUTs for board daisy pool bvt is 0. This has been causing canary failures for the daisy-release-group. slavename: build186-m2 Dead hosts: * chromeos2-row3-rack6-host4 * chromeos2-row3-rack6-host5 * chromeos2-row3-rack6-host6 * chromeos2-row3-rack5-host13 * chromeos2-row3-rack5-host14 * chromeos2-row3-rack5-host15 Assigning to current infra deputy. Although, should this be assigned to Platforms as the DUTs are in chromeos2? Also, feel free to change the label if I got it wrong.
,
Apr 4 2016
,
Apr 4 2016
The duts in BVT pool have been replaced: ~$ dut-status -b daisy -p bvt -g -w chromeos2-row3-rack6-host1 chromeos2-row3-rack6-host3 chromeos2-row3-rack5-host16 chromeos2-row3-rack5-host17 chromeos2-row3-rack5-host19 chromeos2-row3-rack5-host20
,
Apr 4 2016
I suspect that the root cause of this problem is as called out in bug 599158 : The old daisy FSI build isn't stable, and needs to be blacklisted.
,
Apr 4 2016
,
Apr 4 2016
Daisy FSI build R23-2913.212.0 has been blacklisted. That may reduce the drain that caused this problem. However, there's another R23 FSI build that may or may not end up being tested. So, let's keep this bug open until we have solid confirmation that the blacklisting was enough.
,
Apr 26 2016
,
Oct 5 2016
Seems no one cares this bug. Close it now.
,
Oct 7 2016
,
Oct 10 2016
,
Nov 19 2016
,
Jan 21 2017
,
Mar 4 2017
,
Apr 17 2017
,
May 30 2017
,
Aug 1 2017
,
Oct 14 2017
|
|||||||||||||||
►
Sign in to add a comment |
|||||||||||||||
Comment 1 by aaboagye@chromium.org
, Apr 4 2016