Bug 1713260

Summary:	Using abrt-action-analyze-c on core dumps on CI
Product:	[Community] GlusterFS	Reporter:	sankarshan <sankarshan>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	bugs, dkhandel, gluster-infra, ravishankar, sankarshan.mukhopadhyay
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-13 11:29:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description sankarshan 2019-05-23 09:38:02 UTC

Originally pointed out by Yaniv to "run abrt-action-analyze-c on core dumps we have in CI, to see if they are unique or we've seen them before. I have some failure that I'm quite sure has nothing to do with my patch (looks like we try to destroy an xlator that was not initialized?) and it'd be great to use DUPHASH."

Please review this and scope in terms of the work required to enable such.

Comment 1 Worker Ant 2020-03-13 11:29:47 UTC

This bug is moved to https://github.com/gluster/project-infrastructure/issues/44, and will be tracked there from now on. Visit GitHub issues URL for further details