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

Issue 685428 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

crash-reporter: jetstream crash reports not being uploaded

Project Member Reported by lgoo...@chromium.org, Jan 25 2017

Issue description

Starting at build R57-9188, Jetstream crash report uploading seems to be disabled.

Jetstream boards do not have device policy files and instead use an empty /home/chronos/"Consent To Send Stats" to indicate consent.

The crash_sender utility uses 'metrics_client -c' to check for user consent for uploading crash reports. This previously accepted an empty consent file as an indication of consent. A recent change modified this to check that the consent file contains a UUID:

   https://chromium-review.googlesource.com/#/c/422851/

Since the consent file is empty, 'metrics_client -c' now returns a non-zero exit status and the crash report is not uploaded.

Jetstream is tracking this issue on b/34718501.

This is currently only affecting dev channel devices (internal teamfood).

 
Cc: grundler@chromium.org vapier@chromium.org
Components: Internals>CrashReporting Internals>Logging Internals>Metrics
Labels: -Restrict-View-Google OS-Chrome
Owner: grundler@chromium.org
Status: Fixed (was: Untriaged)
pretty sure this has been resolved now:
- the new behavior is what we wanted (empty file == no consent)
- Grant added support to metrics_client to generate a consent id
- Grant updated jetstream to use that new flag to fill out the file correctly

Comment 2 by dchan@chromium.org, Aug 1 2017

Labels: VerifyIn-61

Comment 3 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Sign in to add a comment