New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 621638 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

log the end time of staging, per artifact; run list-files after successful provisions

Project Member Reported by akes...@chromium.org, Jun 20 2016

Issue description

Per 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
 
Labels: -Pri-2 Pri-1
Owner: xixuan@chromium.org
To make more clear what I'm looking for --

When provision gives up on the is_staged call after timeout, it calls the "list-files" rpc against the devserver and then logs the result.

I would like the provision job to make the same call and log the result even if is_staged did *not* timeout. That way we can examine timestamp in the log and determine which was the last artifact to be staged. (I think).
Status: Assigned (was: Untriaged)
Summary: log the end time of staging, per artifact; run list-files after successful provisions (was: log both the start and end time of staging, per artifact; run list-files after successful provisions)

Comment 3 by autumn@chromium.org, Jun 21 2016

Labels: -current-issue
Project Member

Comment 4 by bugdroid1@chromium.org, 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

Labels: Hotlist-CrOS-DevServerLoad
Labels: -dut-health
Status: Fixed (was: Assigned)
Status: Verified (was: Fixed)
Closing. please reopen if its not fixed.

Sign in to add a comment