[Bugs] [Bug 1282847] New: bug-948686.t fails spuriously
bugzilla at redhat.com
bugzilla at redhat.com
Tue Nov 17 15:52:35 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1282847
Bug ID: 1282847
Summary: bug-948686.t fails spuriously
Product: GlusterFS
Version: 3.7.6
Component: tests
Assignee: bugs at gluster.org
Reporter: amukherj at redhat.com
CC: bugs at gluster.org, gluster-bugs at redhat.com
Depends On: 1258714
Blocks: 1258798
+++ This bug was initially created as a clone of Bug #1258714 +++
Description of problem:
bug-948686.t intermittely ends up in a race in GlusterD where one thread
deletes
a stale volume and on a volume start request a start is attempted on the same
object which might be freed up by the other thread. We are considering to use
refcounting mechanism while accessing volinfo objects to get rid of this
problem
but that needs a significant amount of time in development. Till then adding
this test in bad_tests ()
Version-Release number of selected component (if applicable):
Mainline
How reproducible:
Intermittent
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--- Additional comment from Anand Avati on 2015-09-01 01:37:21 EDT ---
REVIEW: http://review.gluster.org/12070 (tests: add bug-948686.t to bad_tests)
posted (#1) for review on master by Atin Mukherjee (amukherj at redhat.com)
--- Additional comment from Anand Avati on 2015-09-01 04:42:34 EDT ---
COMMIT: http://review.gluster.org/12070 committed in master by Raghavendra
Talur (rtalur at redhat.com)
------
commit 99cd07c596f74b1ee8a88c4a43b37eb0921e5fe2
Author: Atin Mukherjee <amukherj at redhat.com>
Date: Tue Sep 1 10:53:19 2015 +0530
tests: add bug-948686.t to bad_tests
bug-948686.t intermittely ends up in a race in GlusterD where one thread
deletes
a stale volume and on a volume start request a start is attempted on the
same
object which might be freed up by the other thread. We are considering to
use
refcounting mechanism while accessing volinfo objects to get rid of this
problem
but that needs a significant amount of time in development. Till then
adding
this test in bad_tests ()
Change-Id: I3ddc025b07c47b17ea75554d5cc809a839365f10
BUG: 1258714
Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
Reviewed-on: http://review.gluster.org/12070
Reviewed-by: Raghavendra Talur <rtalur at redhat.com>
Tested-by: NetBSD Build System <jenkins at build.gluster.org>
Tested-by: Gluster Build System <jenkins at build.gluster.com>
--- Additional comment from Atin Mukherjee on 2015-10-09 13:07:12 EDT ---
http://review.gluster.org/12329 posted for review to remove the test from bad
test
--- Additional comment from Vijay Bellur on 2015-10-12 02:45:07 EDT ---
REVIEW: http://review.gluster.org/12329 (tests: spurious failure fix for
bug-948686.t) posted (#2) for review on master by Atin Mukherjee
(amukherj at redhat.com)
--- Additional comment from Vijay Bellur on 2015-11-16 23:23:54 EST ---
REVIEW: http://review.gluster.org/12329 (tests: spurious failure fix for
bug-948686.t) posted (#3) for review on master by Atin Mukherjee
(amukherj at redhat.com)
--- Additional comment from Vijay Bellur on 2015-11-17 09:36:21 EST ---
COMMIT: http://review.gluster.org/12329 committed in master by Jeff Darcy
(jdarcy at redhat.com)
------
commit 0f35b301fcb539dd85a1dae202b3ce532852d4d6
Author: Atin Mukherjee <amukherj at redhat.com>
Date: Fri Oct 9 22:31:28 2015 +0530
tests: spurious failure fix for bug-948686.t
Ensured import volume and volume start doesn't race in volinfo by
refcounting
volinfo.
Change-Id: I7467eccaba9a00fd63ba0121d8157df24d1c00a6
BUG: 1258714
Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
Reviewed-on: http://review.gluster.org/12329
Tested-by: NetBSD Build System <jenkins at build.gluster.org>
Tested-by: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Jeff Darcy <jdarcy at redhat.com>
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1258714
[Bug 1258714] bug-948686.t fails spuriously
https://bugzilla.redhat.com/show_bug.cgi?id=1258798
[Bug 1258798] bug-948686.t fails spuriously
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list