Make 'reverify_unknown' use repair instead of verify
Reported by
jrbarnette@chromium.org,
Jun 7 2018
|
||||
Issue description
Every 8 hours, we run a job that looks for idle DUTs, and schedules
a verify task to make sure that the DUTs have up-to-date status.
The source for the script is contrib/reverify_unknown.
We should change that script to schedule "repair" in place of "verify":
* For a working DUT, repair does the same thing as verify.
* For a broken DUT, repair will fix the DUT (or mark it definitively
broken) faster than verify.
* Repair tasks will also update DUT labels, meaning DUTs labels will
stay up-to-date even on idle DUTs.
For reference, see bug 849908 for an example where this would have helped
(probably).
,
Jun 11 2018
,
Jun 16 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/2e9747f30574ff4e2425f9029c3056c917e6d88a commit 2e9747f30574ff4e2425f9029c3056c917e6d88a Author: Richard Barnette <jrbarnette@chromium.org> Date: Sat Jun 16 05:16:41 2018 [autotest] Use 'repair' instead of 'verify' in 'reverify_unknown' It turns out that, when checking the status of idle DUTs in the `reverify_unknown` script, it's preferable to use repair tasks in place of verify: * For a working DUT, performance between repair and verify is comparable, and repair will also update DUT labels. * For a broken DUT, repair is faster, because failing verify causes a repair task anyway. BUG= chromium:850734 TEST=None Change-Id: Iab25493a0df9bde05a4a17745ccdf9c45de574f5 Reviewed-on: https://chromium-review.googlesource.com/1102557 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Richard Barnette <jrbarnette@chromium.org> Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org> [modify] https://crrev.com/2e9747f30574ff4e2425f9029c3056c917e6d88a/contrib/reverify_unknown
,
Jun 21 2018
Fixed?
,
Jun 21 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by bugdroid1@chromium.org
, Jun 7 2018