Bug 1473230

Summary:	The netbsd-periodic Jenkins job contains many core files in the archive on failure
Product:	[Community] GlusterFS	Reporter:	Niels de Vos <ndevos>
Component:	tests	Assignee:	bugs <bugs>
Status:	CLOSED EOL	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	atumball, bugs, nigelb, rtalur
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:	2018-09-18 08:14:15 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 Niels de Vos 2017-07-20 09:27:41 UTC

Description of problem:

The https://build.gluster.org/job/netbsd-periodic/ job generates a .tgz on failure (when a new core was detected), but it also contains all the other cores that are under build/install/cores/ . This makes the archive larger than needed, and more difficult to find the correct core.

It would help tremendously if:
- old cores can be deleted before running the tests
- a backtrace is logged in the Jenkins console output (and maybe written to a 
  file in the archive), just like for centos6-regression

Comment 1 Amar Tumballi 2018-09-18 08:14:15 UTC

The job is not running anymore, and not planning to support complete regression on NetBSD for now.