Bug 1332477

Summary:	tests: 'tests/bitrot/br-state-check.t' fails in netbsd
Product:	[Community] GlusterFS	Reporter:	Kotresh HR <khiremat>
Component:	bitrot	Assignee:	bugs <bugs>
Status:	CLOSED EOL	QA Contact:
Severity:	unspecified	Docs Contact:	bugs <bugs>
Priority:	unspecified
Version:	3.7.10	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	NetBSD
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1332473	Environment:
Last Closed:	2017-03-08 10:50:48 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:
Bug Depends On:	1332473
Bug Blocks:

Description Kotresh HR 2016-05-03 10:09:42 UTC

+++ This bug was initially created as a clone of Bug #1332473 +++

Description of problem:
tests/bitrot/br-state-check.t' fails in netbsd

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

How reproducible:
Race, happens sometime

Steps to Reproduce:
1
2.
3.

Actual results:
Genereate core

Expected results:
Should not generate core.

Additional info:

--- Additional comment from Vijay Bellur on 2016-05-03 06:04:32 EDT ---

REVIEW: http://review.gluster.org/14186 (tests: Move tests/bitrot/br-state-check.t to bad test) posted (#1) for review on master by Kotresh HR (khiremat)

--- Additional comment from Vijay Bellur on 2016-05-03 06:06:16 EDT ---

REVIEW: http://review.gluster.org/14186 (tests: Move tests/bitrot/br-state-check.t to bad test) posted (#2) for review on master by Kotresh HR (khiremat)

Comment 1 Vijay Bellur 2016-05-03 10:11:08 UTC

REVIEW: http://review.gluster.org/14187 (tests: Move tests/bitrot/br-state-check.t to bad test) posted (#1) for review on release-3.7 by Kotresh HR (khiremat)

Comment 2 Kaushal 2017-03-08 10:50:48 UTC

This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.