Make repair tasks check/update DUT labels
Reported by
jrbarnette@chromium.org,
Mar 19 2018
|
|||
Issue description
Repair special tests should include running automated label
detection/assignment. There are at least two reasons:
* From time to time, we find that DUTs can acquire incorrect
labels due to prior errors. When that happens, we need a way
to force running label detection. Running repair is an easy
way to deal with that.
* If repair fixes a DUT that's been out of service for some
period of time, its labels may become out of date. So, repair
should make sure the labels are accurate.
,
Mar 20 2018
This should be done, except for the push to prod. Heaven only knows when that will happen, but it should be before the next time that we need the feature.
,
May 7 2018
,
May 8 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/7cd9c5c46a49d77b375c01d40b1e46b4adf877cf commit 7cd9c5c46a49d77b375c01d40b1e46b4adf877cf Author: Richard Barnette <jrbarnette@chromium.org> Date: Tue May 08 00:24:02 2018 [autotest] Fix updating labels in repair. A previous change was meant to force labels to be updated after a successful repair. That change never worked. This fixes it. BUG= chromium:823454 TEST=run repair in a local instance, see label updates run Change-Id: I8e7b406c18538ea6c409f387c8b0cc96112fe760 Reviewed-on: https://chromium-review.googlesource.com/1045915 Commit-Ready: Richard Barnette <jrbarnette@chromium.org> Tested-by: Richard Barnette <jrbarnette@chromium.org> Reviewed-by: Xixuan Wu <xixuan@chromium.org> [modify] https://crrev.com/7cd9c5c46a49d77b375c01d40b1e46b4adf877cf/server/control_segments/repair
,
May 23 2018
Confirmed fixed this time. Sample repair task, with logs showing
the label detection code running:
https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/hosts/chromeos6-row4-rack11-host2/1105670-repair/20182305112909/debug/
|
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Mar 20 2018