Description of problem: EXPECT_WITHIN did string match in one place and regex in other. Leading to incorrect looping in many testcase. Fix it. 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/15315 (tests: fix EXPECT_WITHIN) posted (#1) for review on master by Anuradha Talur (atalur)
REVIEW: http://review.gluster.org/15315 (tests: fix EXPECT_WITHIN) posted (#2) for review on master by Anuradha Talur (atalur)
REVIEW: http://review.gluster.org/15315 (tests: fix EXPECT_WITHIN) posted (#3) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/15341 (tests: Fix spurious failure of ec-root-heal.t) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/15341 (tests: Fix spurious failures because of wrong shd up function) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/15315 (tests: fix EXPECT_WITHIN) posted (#4) for review on master by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/15341 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit 63d24908e01b24cc21bea584fed4b719fca865f3 Author: Pranith Kumar K <pkarampu> Date: Tue Aug 30 02:02:45 2016 +0530 tests: Fix spurious failures because of wrong shd up function Fixed the way shd up check is done to prevent self-heal daemon not running error when heal full command is executed. Change-Id: I93c4a0da12316373d62cd4ea74432cd9bf2b090c BUG: 1370053 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/15341 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Anuradha Talur <atalur>
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.9.0, please open a new bug report. glusterfs-3.9.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/2016-November/029281.html [2] https://www.gluster.org/pipermail/gluster-users/