Bug 1600963

Summary:	get the failed test details into gerrit output itself
Product:	[Community] GlusterFS	Reporter:	Amar Tumballi <atumball>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	amukherj, bugs, gluster-infra, jeff, nigelb, srangana
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	Process-Automation
Fixed In Version:	glusterfs-5.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-05 06:18:52 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 Amar Tumballi 2018-07-13 13:22:16 UTC

# Description of problem:

It would be great to get all the tests which failed in regression in gerrit output, instead of just SUCCESS or FAILURE.

# Additional info:

This helps the people to notice the failures in gerrit, without going out to build output (which not many people do).

Comment 1 Shyamsundar 2018-07-13 14:57:41 UTC

There are several bugs of the same nature #1576161 and #1570576.

I am thinking that we need a generic request/action to post failure onto gerrit itself, rather than having to goto Jenkins.

Now, this may help for some cases, and in some other (possibly cores etc.) contributors would need to get to Jenkins, which  is fine, but reduces the need to visit Jenkins.

Comment 2 Worker Ant 2018-07-16 03:36:30 UTC

REVIEW: https://review.gluster.org/20513 (run-tests.sh: provide option to write 'failure' output to a file) posted (#2) for review on master by Amar Tumballi

Comment 3 Worker Ant 2018-07-17 17:07:29 UTC

COMMIT: https://review.gluster.org/20513 committed in master by "Shyamsundar Ranganathan" <srangana> with a commit message- run-tests.sh: provide option to write 'failure' output to a file

Change-Id: I42f5e0f3513ba758a09b1a7330e49fc3c8fc218e
updates: bz#1600963
Signed-off-by: Amar Tumballi <amarts>

Comment 4 Shyamsundar 2018-10-23 15:14:36 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.0, please open a new bug report.

glusterfs-5.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/