Description of problem: The test mentioned failed in following CI regression run https://build.gluster.org/job/regression-test-burn-in/1682/consoleFull Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/15457 (tests: fix bug-963541.t spurious failure) posted (#1) for review on master by Atin Mukherjee (amukherj)
COMMIT: http://review.gluster.org/15457 committed in master by Vijay Bellur (vbellur) ------ commit 0ed0a560097426a0e20eb533f1018b8d6a5c08c0 Author: Atin Mukherjee <amukherj> Date: Sun Sep 11 20:16:33 2016 +0530 tests: fix bug-963541.t spurious failure wait for remove brick to complete before attempt for a commit. Change-Id: I66ea6c48b6a69fe33d79f9d9080b6f2c1462578e BUG: 1374993 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: http://review.gluster.org/15457 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Vijay Bellur <vbellur>
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.10.0, please open a new bug report. glusterfs-3.10.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/gluster-users/2017-February/030119.html [2] https://www.gluster.org/pipermail/gluster-users/