Bug 1530111

Summary:	Logs unavailable if a regression run was aborted
Product:	[Community] GlusterFS	Reporter:	Nithya Balachandran <nbalacha>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-infra, nigelb
Target Milestone:	---
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-07-20 04:47:44 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 Nithya Balachandran 2018-01-02 04:59:02 UTC

Description of problem:

The gluster logs are unavailable if a regression run was aborted.

Eg: https://build.gluster.org/job/centos6-regression/8171/console

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Nigel Babu 2018-07-20 04:47:44 UTC

I'm going to WONTFIX this. With the advent of per test timeouts, we will no longer abort the entire regression job. This is not a problem we have to spend a lot of time solving.