Description of problem: Since last few days I have been observing netbsd runs getting aborted because of lock_revocation.t which gets hung. One of many such instances: https://build.gluster.org/job/netbsd7-regression/3/console Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
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
Reducing the priority to low as there is proposal to drop regressions on NetBSD.
We dropped NetBSD support