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

Issue 783029 link

Starred by 1 user
Status: Archived
Owner:
snanda@chromium.org
Closed: Jun 2018
Cc:
█ dshi@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

0-length kernel crashdumps -- are these being throtted to 0?

Project Member Reported by akes...@chromium.org, Nov 9 2017 
Example: https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/hosts/chromeos2-row4-rack2-host16/1149355-repair/20170811170946/crashinfo.chromeos2-row4-rack2-host16

A repair job after a failed provision. The status log talks about orphaned crash dumps, and these empty crash dump files are there. Are they empty because of throttling?

Comment 1 by dshi@chromium.org, Nov 9 2017 

From the summary:
https://storage.cloud.google.com/chromeos-autotest-results/hosts/chromeos2-row4-rack2-host16/1149355-repair/20170811170946/result_summary.html

The result is not throttled, so these empty dump can't be caused by result throttling. Also, when result throttle delete files, it doesn't leave 0 size file behind. The file entry is removed, and only trace it can be found is in result_summary.html.

Comment 2 by akes...@chromium.org, Nov 9 2017

Cc: dshi@chromium.org
Owner: snanda@chromium.org
Thanks.

-> snanda@ is there someone on kernel team who can comment on why these 0-byte kernelcrash files are being dropped? It would sure be a lot more helpful if they were not 0-byte.

Comment 3 by cindyb@chromium.org, May 31 2018 

Hi, this bug has not been updated recently and remains untriaged. Please acknowledge the bug and provide status within two weeks (6/8/2018), or the bug will be closed. Thank you.

Comment 4 by cindyb@chromium.org, Jun 8 2018

Status: Archived (was: Untriaged)
Archiving per #3
►

Sign in to add a comment