Bug 1337777 - tests/bugs/write-behind/1279730.t fails spuriously
Summary: tests/bugs/write-behind/1279730.t fails spuriously
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: write-behind
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Csaba Henk
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1337779 1337780 1337781 1426046
TreeView+ depends on / blocked
 
Reported: 2016-05-20 05:04 UTC by Raghavendra G
Modified: 2018-08-29 03:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1337779 1337780 1337781 1426046 (view as bug list)
Environment:
Last Closed: 2018-08-29 03:54:08 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Raghavendra G 2016-05-20 05:04:21 UTC
Description of problem:

14:35:56 [21:35:56] Running tests in file ./tests/bugs/write-behind/bug-1279730.t
14:36:00 No volumes present
14:36:01 read should've failed as previous write would've failed with EDQUOT, but its successfultar: Removing leading `/' from member names
14:36:03 ./tests/bugs/write-behind/bug-1279730.t .. 
14:36:03 1..15
14:36:03 ok 1, LINENUM:10
14:36:03 ok 2, LINENUM:11
14:36:03 ok 3, LINENUM:12
14:36:03 ok 4, LINENUM:14
14:36:03 ok 5, LINENUM:15
14:36:03 ok 6, LINENUM:16
14:36:03 ok 7, LINENUM:17
14:36:03 ok 8, LINENUM:18
14:36:03 ok 9, LINENUM:19
14:36:03 ok 10, LINENUM:21
14:36:03 ok 11, LINENUM:24
14:36:03 not ok 12 , LINENUM:26
14:36:03 FAILED COMMAND: ./tests/bugs/write-behind/bug-1279730 /mnt/glusterfs/0/file "gluster --mode=script --wignore volume quota patchy limit-usage / 1024"
14:36:03 ok 13, LINENUM:28
14:36:03 ok 14, LINENUM:30
14:36:03 ok 15, LINENUM:31
14:36:03 Failed 1/15 subtests 
14:36:03 
14:36:03 Test Summary Report
14:36:03 -------------------
14:36:03 ./tests/bugs/write-behind/bug-1279730.t (Wstat: 0 Tests: 15 Failed: 1)
14:36:03   Failed test:  12
14:36:03 Files=1, Tests=15,  7 wallclock secs ( 0.02 usr  0.00 sys +  1.18 cusr  0.39 csys =  1.59 CPU)
14:36:03 Result: FAIL
14:36:03 End of test ./tests/bugs/write-behind/bug-1279730.t

Version-Release number of selected component (if applicable):


How reproducible:
inconsistent, but surely there is some race causing this issue.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Vijay Bellur 2016-05-20 05:05:52 UTC
REVIEW: http://review.gluster.org/14443 (tests/write-behind: move 1279730.t to BAD tests) posted (#1) for review on master by Raghavendra G (rgowdapp)

Comment 2 Vijay Bellur 2016-05-30 09:12:22 UTC
COMMIT: http://review.gluster.org/14443 committed in master by Raghavendra G (rgowdapp) 
------
commit 4c798e87859d826bdf048d93a38830a74aa04752
Author: Raghavendra G <rgowdapp>
Date:   Fri May 20 10:29:05 2016 +0530

    tests/write-behind: move 1279730.t to BAD tests
    
    There is a race condition which is causing the test to fail. For lack
    of bandwidth I am moving this test to BAD, though clearly there is
    some issue with codebase.
    
    BUG: 1337777
    Change-Id: If4f3eff8a5985f37a4dee65d2df29fa7b6bda7ae
    Signed-off-by: Raghavendra G <rgowdapp>
    Reviewed-on: http://review.gluster.org/14443
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>

Comment 3 Amar Tumballi 2018-08-29 03:54:08 UTC
Lot of time since no activity on this bug. We have either fixed it already or it is mostly not critical anymore!

Please re-open the bug if the issue is burning for you, or you want to take the bug to closure with fixes.


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