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

Issue 652211 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

move CrOS_update_... log out of sysinfo/ and into root of log directory

Project Member Reported by akes...@chromium.org, Oct 3 2016

Issue description

I think this log does not belong in sysinfo/ for a few reasons

1) It is not produced on the DUT, unlike the other logs there.
2) It is generally much more important than most of those logs, and is one of the first thinkgs you want to look at when diagnosing provision.
3) sysinfo/ often gets tarballed up if it gets above a certain size. This makes it really painful to dig into a provision failure (requires sshing into desktop machine, using gsutil to download tarball, inspecting, etc).
 
Cc: dshi@chromium.org jrbarnette@chromium.org
I agree, which directory is better?
Either the root directory of the log, or maybe in some directory called "devserver_logs" or something to make it obvious.
Status: Assigned (was: Untriaged)
Labels: -current-issue
Project Member

Comment 6 by bugdroid1@chromium.org, Oct 10 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/95c6cce5c3debfc7bd98f27450916c78390f28c6

commit 95c6cce5c3debfc7bd98f27450916c78390f28c6
Author: xixuan <xixuan@chromium.org>
Date: Thu Oct 06 00:49:41 2016

autotest: save devserver logs for auto-update to directory autoupdate_logs

Previously, devserver logs of auto-update is saved in sysinfo, which is
sometimes zipped and hard to diagnose in browser.

This CL changes 'sysinfo' to directory 'autoupdate_logs' and save the CrOS
Auto-Update logs there.

BUG= chromium:652211 
TEST=run jobs in local workstation and make sure that CrOS_update_***.log exist
in directory 'autoupdate_logs'.
Run unittest.

Change-Id: Ia0702a916374417284294bf4bc7ff5d86d8a0bf5
Reviewed-on: https://chromium-review.googlesource.com/394268
Commit-Ready: Xixuan Wu <xixuan@chromium.org>
Tested-by: Xixuan Wu <xixuan@chromium.org>
Reviewed-by: Allen Li <ayatane@chromium.org>

[modify] https://crrev.com/95c6cce5c3debfc7bd98f27450916c78390f28c6/server/hosts/cros_host.py
[modify] https://crrev.com/95c6cce5c3debfc7bd98f27450916c78390f28c6/client/common_lib/cros/dev_server.py
[modify] https://crrev.com/95c6cce5c3debfc7bd98f27450916c78390f28c6/client/common_lib/cros/dev_server_unittest.py

Status: Fixed (was: Assigned)
Project Member

Comment 8 by bugdroid1@chromium.org, Jan 13 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/79e1659eb156d68b187d6fde0f11a648b1279528

commit 79e1659eb156d68b187d6fde0f11a648b1279528
Author: xixuan <xixuan@google.com>
Date: Wed Dec 14 09:54:53 2016

autotest: make autoupdate_logs never be zipped.

It's hard to check autoupdate_logs if it's zipped. This CL makes this folder
never be zipped.

BUG= chromium:652211 
TEST=None

Change-Id: I63e6816512cb843526c3484feeda325a2d77e148
Reviewed-on: https://chromium-review.googlesource.com/419940
Commit-Ready: Xixuan Wu <xixuan@chromium.org>
Tested-by: Xixuan Wu <xixuan@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>

[modify] https://crrev.com/79e1659eb156d68b187d6fde0f11a648b1279528/site_utils/gs_offloader.py

Comment 9 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58

Comment 10 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 11 by dchan@google.com, May 30 2017

Labels: VerifyIn-60
Labels: VerifyIn-61

Comment 13 by dchan@chromium.org, Oct 14 2017

Status: Archived (was: Fixed)

Sign in to add a comment