Description of problem: Mark test case ./tests/bugs/bug-1371806_1.t as a bad test case. Version-Release number of selected component (if applicable): How reproducible: Sometime test case ./tests/bugs/bug-1371806_1.t is failing so we are marking it as a bad test case. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/18450 (test: Mark test case ./tests/bugs/bug-1371806_1.t as a bad test case) posted (#1) for review on master by MOHIT AGRAWAL (moagrawa)
COMMIT: https://review.gluster.org/18450 committed in master by Jeff Darcy (jeff.us) ------ commit d561282633801bf3254c057188b7f18c7c6fe7c6 Author: Mohit Agrawal <moagrawa> Date: Mon Oct 9 14:10:52 2017 +0530 test: Mark test case ./tests/bugs/bug-1371806_1.t as a bad test case Problem: Test case ./tests/bugs/bug-1371806_1.t is failing. Solution: Mark test case ./tests/bugs/bug-1371806_1.t as a bad test case. BUG: 1499663 Change-Id: Icb3f41d23dcc74cce6fde05ca343c158d5f58cdd Signed-off-by: Mohit Agrawal <moagrawa>
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.13.0, please open a new bug report. glusterfs-3.13.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-December/000087.html [2] https://www.gluster.org/pipermail/gluster-users/