Description of problem: basic/ec/ec-background-heal.t fails spuriously. Version-Release number of selected component (if applicable): mainline How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/16470 (cluster/ec: mark ec-background-heal.t as bad) posted (#1) for review on master by Xavier Hernandez (xhernandez)
COMMIT: https://review.gluster.org/16470 committed in master by Xavier Hernandez (xhernandez) ------ commit 9e2d7faf598078d12a47512abae6792adbe01aca Author: Xavier Hernandez <xhernandez> Date: Thu Jan 26 10:24:32 2017 +0100 cluster/ec: mark ec-background-heal.t as bad Change-Id: I0c54c62cdeb40b983da2392296762471a5474652 BUG: 1416689 Signed-off-by: Xavier Hernandez <xhernandez> Reviewed-on: https://review.gluster.org/16470 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Atin Mukherjee <amukherj> CentOS-regression: Gluster Build System <jenkins.org>
*** Bug 1419443 has been marked as a duplicate of this bug. ***
Although this bug is tracked against mainline, I backported the commit to mark this test as bad in release-3.10 as well. This is to ensure we do not get spurious failures against commits for that branch. The Bug used to make this change is #1419696 Request any fix to be back ported and the test unblocked as appropriate.
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/