I started the week to a large number of devices that died slowly and were not auto-repaired.
Using this bug to track all of those and chase specific root causes separately.
This bug should be closed at the end of the week as this is only an incident report bug.
> pprabhu@pprabhu:chromiumos$ dut-status -m stout -p bvt -n | xargs -i dut-status -g {}
That's a lot of unnecessary circumlocution. This is equivalent:
$ dut-status -m stout -p bvt -n -g
Looking at the failures, they seem spread out over several days with
distinct patterns, so probably there's not a single root cause.
> (2) Does stout have no servo support overall?
Stout has no servo support at all.
Comment 1 by pprabhu@chromium.org
, Mar 5 2018nasher: pprabhu@pprabhu:chromiumos$ dut-status -m nasher -p bvt -n | xargs -i dut-status -g {} chromeos2-row4-rack9-host2 2018-03-01 16:27:16 NO http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row4-rack9-host2/296414-repair/ 2018-03-01 15:49:45 -- http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row4-rack9-host2/295732-provision/ 2018-03-01 15:47:21 OK http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row4-rack9-host2/295678-repair/ chromeos2-row4-rack9-host11 2018-02-24 02:07:11 NO http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row4-rack9-host11/187019-repair/ 2018-02-24 01:27:28 -- http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row4-rack9-host11/186423-provision/ 2018-02-24 01:26:50 OK http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row4-rack9-host11/186405-cleanup/ chromeos2-row4-rack9-host12 2018-02-28 00:15:18 NO http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row4-rack9-host12/270827-repair/ 2018-02-27 23:22:11 -- http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row4-rack9-host12/269683-provision/ 2018-02-27 22:41:31 OK http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row4-rack9-host12/269017-repair/ chromeos2-row4-rack9-host17 2018-02-28 22:58:15 NO http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row4-rack9-host17/286368-repair/ 2018-02-28 20:50:45 -- http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row4-rack9-host17/284215-provision/ 2018-02-28 19:42:07 OK http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row4-rack9-host17/283516-cleanup/ chromeos2-row4-rack10-host16 2018-02-27 22:28:21 NO http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row4-rack10-host16/268811-repair/ 2018-02-27 21:54:58 -- http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row4-rack10-host16/268138-provision/ 2018-02-27 21:28:17 OK http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row4-rack10-host16/267657-repair/ 2 of these are issue 695151 where chromeos-install fails due to disk corruption. In one instance, image failed to bot from USB Another one had no servo support (the servo was likely down)