log the end time of staging, per artifact; run list-files after successful provisions |
|||||||
Issue descriptionPer discussion with dshi@ When staging takes a long time but eventually succeeds, we don't have an easy way of knowing which artifact was the last one to be staged. It is necessary to track down the devserver that was used for that and examine its server.log
,
Jun 20 2016
,
Jun 21 2016
,
Jun 21 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/2cd33fff8fdd0a8f2aad9c1a5314dcd9e42142fa commit 2cd33fff8fdd0a8f2aad9c1a5314dcd9e42142fa Author: xixuan <xixuan@google.com> Date: Tue Jun 21 00:41:16 2016 Autotest: list contents of the staged image directory in devserver. This CL lists the detailed file contents of the staged image directory in devserver, whether the stage call is failed or not this time. BUG= chromium:621638 TEST=run local autotest, use moblab as devserver to test whether logging exist when job provision_autoupdate fails or succeeds. Change-Id: I19d7b6a6b8ba0c55f5dde2155d14a0b90cdce5f2 Reviewed-on: https://chromium-review.googlesource.com/354211 Commit-Ready: Xixuan Wu <xixuan@chromium.org> Tested-by: Xixuan Wu <xixuan@chromium.org> Reviewed-by: Dan Shi <dshi@google.com> [modify] https://crrev.com/2cd33fff8fdd0a8f2aad9c1a5314dcd9e42142fa/server/site_tests/provision_AutoUpdate/provision_AutoUpdate.py
,
Jun 21 2016
,
Jun 21 2016
,
Jun 30 2016
,
Aug 12 2016
Closing. please reopen if its not fixed. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by akes...@chromium.org
, Jun 20 2016Owner: xixuan@chromium.org