stable image update cron job doesn't report its errors
Reported by
jrbarnette@chromium.org,
Oct 25 2016
|
||||||||
Issue description
Last night, the stable versions update cron job failed
part way through. Here's all that was in the mail:
Default R54-8743.65.0 -> R54-8743.69.0
Applying stable version changes:
celes (default) -> R54-8743.69.1
The full log file from the run is attached; it shows a failure:
AttributeError: '_CrosVersionMap' object has no attribute 'set_stable_version'
The problem is that the script doesn't redirect stderr to the e-mail
file:
date
$ASSIGN_STABLE "${OPTIONS[@]}" | tee ${TMPFILE}
echo
,
Nov 5 2016
,
Nov 16 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/31acd2ea3a7c62d74005ec80e62db99ab5d92fcd commit 31acd2ea3a7c62d74005ec80e62db99ab5d92fcd Author: Richard Barnette <jrbarnette@chromium.org> Date: Sat Nov 05 00:10:25 2016 [autotest] Include stderr in run-stable-update e-mail. This changes the script that updates repair images so that the e-mail message will include standard error from the update script, to make errors actually detectable. BUG= chromium:659171 TEST=run the cron script locally Change-Id: Ied1db8053a4bf9e42f70f6e89d6533fd69e81a6e Reviewed-on: https://chromium-review.googlesource.com/407884 Commit-Ready: Richard Barnette <jrbarnette@chromium.org> Tested-by: Richard Barnette <jrbarnette@chromium.org> Reviewed-by: Shuqian Zhao <shuqianz@chromium.org> [modify] https://crrev.com/31acd2ea3a7c62d74005ec80e62db99ab5d92fcd/contrib/run-stable-update
,
Jan 10 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 dshi@chromium.org
, Oct 25 2016Owner: jrbarnette@chromium.org