Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1614718

Summary:	Fix spurious failures in tests/bugs/index/bug-1559004-EMLINK-handling.t
Product:	[Community] GlusterFS	Reporter:	Pranith Kumar K <pkarampu>
Component:	tests	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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-23 15:16: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 Pranith Kumar K 2018-08-10 09:46:39 UTC

Description of problem:
20:09:33 [20:09:37] Running tests in file ./tests/bugs/index/bug-1559004-EMLINK-handling.t
20:09:33 Timeout set is 1200, default 300
20:29:33 ./tests/bugs/index/bug-1559004-EMLINK-handling.t timed out after 1200 seconds
20:29:33 ./tests/bugs/index/bug-1559004-EMLINK-handling.t: bad status 124

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2018-08-10 09:48:34 UTC

REVIEW: https://review.gluster.org/20699 (tests: Increase timeout to 30 minutes to handle lcov slowness) posted (#1) for review on master by Pranith Kumar Karampuri

Comment 2 Worker Ant 2018-08-16 06:13:44 UTC

COMMIT: https://review.gluster.org/20699 committed in master by "Amar Tumballi" <amarts> with a commit message- tests: Increase timeout to 30 minutes to handle lcov slowness

This script on a normal setup takes 15 minutes. With lcov it needs
to be increased. Considering we did 1.5X of the default $run_timeout
in run-tests.sh, I am doing the same for this script.

fixes bz#1614718
Change-Id: Ia571b33ff13deb8cbd8e48561769e876aa0b1aff
Signed-off-by: Pranith Kumar K <pkarampu>

Comment 3 Shyamsundar 2018-10-23 15:16:52 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/