[Bugs] [Bug 1368421] lock_revocation.t is causing netbsd runs to abort

bugzilla at redhat.com bugzilla at redhat.com
Fri Aug 19 12:02:53 UTC 2016


https://bugzilla.redhat.com/show_bug.cgi?id=1368421

Nigel Babu <nigelb at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nigelb at redhat.com



--- Comment #1 from Nigel Babu <nigelb at redhat.com> ---
These are the failures where we hang at tests


FAILURE on http://build.gluster.org/job/netbsd7-regression/38/consoleText
nbslave7g.cloud.gluster.org
Running tests in file ./tests/features/lock_revocation.t

FAILURE on http://build.gluster.org/job/netbsd7-regression/33/consoleText
nbslave7g.cloud.gluster.org
Running tests in file ./tests/basic/afr/granular-esh/add-brick.t

FAILURE on http://build.gluster.org/job/netbsd7-regression/21/consoleText
nbslave7c.cloud.gluster.org
Running tests in file ./tests/features/lock_revocation.t

FAILURE on http://build.gluster.org/job/netbsd7-regression/17/consoleText
nbslave7g.cloud.gluster.org
Running tests in file ./tests/basic/afr/split-brain-favorite-child-policy.t

FAILURE on http://build.gluster.org/job/netbsd7-regression/13/consoleText
nbslave7j.cloud.gluster.org
Running tests in file ./tests/features/lock_revocation.t

FAILURE on http://build.gluster.org/job/netbsd7-regression/12/consoleText
nbslave79.cloud.gluster.org
Running tests in file ./tests/features/lock_revocation.t

FAILURE on http://build.gluster.org/job/netbsd7-regression/5/consoleText
nbslave74.cloud.gluster.org
Running tests in file ./tests/features/lock_revocation.t

FAILURE on http://build.gluster.org/job/netbsd7-regression/4/consoleText
nbslave74.cloud.gluster.org
Running tests in file ./tests/basic/afr/add-brick-self-heal.t

FAILURE on http://build.gluster.org/job/netbsd7-regression/3/consoleText
nbslave7h.cloud.gluster.org
Running tests in file ./tests/features/lock_revocation.t

-- 
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