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

Issue 772315 link

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



Sign in to add a comment

lsb-release and os-release files being categorized as orphaned crash dumps?

Project Member Reported by akes...@chromium.org, Oct 6 2017 
Example: https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/hosts/chromeos2-row7-rack6-host11/1239880-repair/20170510232158/

	START	----	repair.servoreset	timestamp=1507272038	localtime=Oct 05 23:40:38	
		INFO	----	----	timestamp=1507272073	localtime=Oct 05 23:41:13	Start crashcollection record
		INFO	----	Orphaned Crash Dump	timestamp=1507272073	localtime=Oct 05 23:41:13	/var/spool/crash/lsb-release
		INFO	----	Orphaned Crash Dump	timestamp=1507272073	localtime=Oct 05 23:41:13	/var/spool/crash/os-release
		INFO	----	----	timestamp=1507272073	localtime=Oct 05 23:41:13	End crashcollection record
		GOOD	----	verify.ssh	timestamp=1507272096	localtime=Oct 05 23:41:36	
	END GOOD	----	repair.servoreset	timestamp=1507272096	localtime=Oct 05 23:41:36	



Examining the contents of those collected files, they certainly don't look like crash dumps.

Comment 1 by dshi@chromium.org, Oct 6 2017 

The logic is to collect all files in crash dir and consider them to be crash dumps:
https://cs.corp.google.com/android/external/autotest/server/site_crashcollect.py?rcl=3e44768d2ace0b33f720c8403b248c04f13a9111&l=171

    return host.list_files_glob(os.path.join(constants.CRASH_DIR, '*'))

We can exclude lsb-release and os-release if we want to.

Comment 2 by akes...@chromium.org, Oct 6 2017 

Maybe my question should be why these are ending up in the crash dir.

Comment 3 by dshi@chromium.org, Oct 6 2017 

Who knows ChromeOS crash dumps? That seems to be some OS thing.

Comment 4 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 5 by jrbarnette@chromium.org, Jun 1 2018

Status: Archived (was: Untriaged)
►

Sign in to add a comment