Make a verifier to check for old builds
Reported by
jrbarnette@chromium.org,
Mar 25 2016
|
|||||
Issue description
Recently, I observed a repair failure. The log is here:
https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/hosts/chromeos2-row4-rack10-host11/333440-repair/20162503085442/
The status.log file is attached.
The reason for the failure is at least in part that the DUT is
running really old software:
localhost ~ # cat /etc/lsb-release
CHROMEOS_RELEASE_APPID={D851316B-7E57-4805-A7CE-01829AC1443E}
CHROMEOS_RELEASE_BOARD=daisy
CHROMEOS_RELEASE_DESCRIPTION=2913.212.0 (Official Build) dev-channel daisy test
CHROMEOS_RELEASE_NAME=Chrome OS
CHROMEOS_RELEASE_TRACK=testimage-channel
CHROMEOS_RELEASE_VERSION=2913.212.0
GOOGLE_RELEASE=2913.212.0
CHROMEOS_AUSERVER=https://tools.google.com/service/update2
CHROMEOS_DEVSERVER=
We need a check with a repair dependency of some sort that says "if
the build is really old, AU to the repair image, no questions asked."
,
Apr 5 2016
The build in question has been blacklisted from testing, for reasons
not directly related to this failure.
Depending on whether we continue testing other R23 builds, the
change requested here may be obviated.
Assuming that we continue to need to install older FSI builds, we
may or may not want to do this:
* This particular problem happened because the old build failed
to update. That sort of failure is supposed to be rare. When
it isn't rare, it's evidence that the build should be blacklisted
(as for the build cited in this bug).
* Even if we believe that this will happen often enough to be worth
noticing, it's possible that the fix applied for bug 599158 is
better. That change says "ignore the errors from the old build,
and let it update."
Holding this open for further consideration, but this could wind up
"WontFix".
,
Apr 26 2016
,
May 31 2016
Blacklisting the problem builds has made this lower priority.
,
Jun 1 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 13 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by autumn@chromium.org
, Mar 28 2016