Description of problem: Too many aborted runs due to said test case, and hence need to mark this as bad (this is done on master as well).
REVIEW: https://review.gluster.org/17360 (tests/lock_revocation: mark as bad) posted (#1) for review on release-3.11 by Shyamsundar Ranganathan (srangana)
REVIEW: https://review.gluster.org/17360 (tests/lock_revocation: mark as bad) posted (#2) for review on release-3.11 by Shyamsundar Ranganathan (srangana)
COMMIT: https://review.gluster.org/17360 committed in release-3.11 by Shyamsundar Ranganathan (srangana) ------ commit 25a5333f5315106fc06aa82abb7dce96a54b64e6 Author: Raghavendra G <rgowdapp> Date: Wed May 10 15:44:33 2017 +0530 tests/lock_revocation: mark as bad The test is failing in master. Looks like a hang causing Aborted test runs. > Reviewed-on: https://review.gluster.org/17234 (cherry picked from commit d5865881de5653a0e810093a9867ab3962d00f67) Change-Id: I7a589ad2c54bd55d62f4e66fdf8037c19fc123ea BUG: 1454533 Reviewed-on: https://review.gluster.org/17360 Tested-by: Shyamsundar Ranganathan <srangana> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Smoke: Gluster Build System <jenkins.org> Reviewed-by: Shyamsundar Ranganathan <srangana>
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-3.11.0, please open a new bug report. glusterfs-3.11.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] http://lists.gluster.org/pipermail/announce/2017-May/000073.html [2] https://www.gluster.org/pipermail/gluster-users/