Bug 1499663 - Mark test case ./tests/bugs/bug-1371806_1.t as a bad test case.
Summary: Mark test case ./tests/bugs/bug-1371806_1.t as a bad test case.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: tests
Version: mainline
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Mohit Agrawal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-09 08:34 UTC by Mohit Agrawal
Modified: 2017-12-08 17:43 UTC (History)
1 user (show)

Fixed In Version: glusterfs-3.13.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-08 17:43:00 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Mohit Agrawal 2017-10-09 08:34:09 UTC
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:

Comment 1 Worker Ant 2017-10-09 08:42:35 UTC
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)

Comment 2 Worker Ant 2017-10-09 18:12:07 UTC
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>

Comment 3 Shyamsundar 2017-12-08 17:43:00 UTC
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/


Note You need to log in before you can comment on or make changes to this bug.