Bug 1332045 - multiple failures for testcase: tests/basic/quota.t
Summary: multiple failures for testcase: tests/basic/quota.t
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: quota
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Raghavendra G
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1366472
TreeView+ depends on / blocked
 
Reported: 2016-05-01 17:49 UTC by Susant Kumar Palai
Modified: 2018-08-29 03:53 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1366472 (view as bug list)
Environment:
Last Closed: 2018-08-29 03:53:45 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Susant Kumar Palai 2016-05-01 17:49:42 UTC
Description of problem:
multiple failures for testcase: tests/basic/quota.t.

Link to failures:
https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/16439/consoleFull

https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/16440/console

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Vijay Bellur 2016-05-01 17:58:32 UTC
REVIEW: http://review.gluster.org/14136 (quota: mark tests/basic/quota.t as bad_test) posted (#1) for review on master by Susant Palai (spalai)

Comment 2 Vijay Bellur 2016-05-01 18:12:42 UTC
REVIEW: http://review.gluster.org/14136 (quota: mark tests/basic/quota.t as bad_test) posted (#2) for review on master by Susant Palai (spalai)

Comment 3 Niels de Vos 2016-05-01 20:37:22 UTC
Adding the 'tracking' keyword so that our bug-status-check-script does not triple over it. Please remove the keyword when progress on this bug is made.

Comment 4 Vijay Bellur 2016-05-02 01:04:20 UTC
COMMIT: http://review.gluster.org/14136 committed in master by Niels de Vos (ndevos) 
------
commit f1f6a0e2b09884151c37434bd512cb1482608218
Author: Susant Palai <spalai>
Date:   Sun May 1 23:23:44 2016 +0530

    quota: mark tests/basic/quota.t as bad_test
    
    tests/basic/quota.t regularly leaves a core behind.
    Some of the failed tests:
    * https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/16439/consoleFull
    * https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/16440/console
    
    Change-Id: Iacf42c40f768dd2939994bbb87cc7ef366ee495f
    BUG: 1332045
    Signed-off-by: Susant Palai <spalai>
    Reviewed-on: http://review.gluster.org/14136
    Reviewed-by: Niels de Vos <ndevos>
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>

Comment 5 Vijaikumar Mallikarjuna 2016-05-02 08:46:49 UTC
Look at the stack trace of the corefile, some memory corruption in synctask framework

#0  0xbb4104b7 in ?? ()
(gdb) bt
#0  0xbb4104b7 in ?? ()
#1  0xbb410458 in ?? ()
#2  0x00000004 in ?? ()
#3  0x00000006 in ?? ()
#4  0xbb457084 in ?? ()
#5  0xbb759119 in synctask_destroy (task=0xb8a18030) at /home/jenkins/root/workspace/rackspace-netbsd7-regression-triggered/libglusterfs/src/syncop.c:391
#6  0xbb759195 in synctask_done (task=0xb8a18030) at /home/jenkins/root/workspace/rackspace-netbsd7-regression-triggered/libglusterfs/src/syncop.c:409
#7  0xbb759a81 in synctask_switchto (task=0xb8a18030) at /home/jenkins/root/workspace/rackspace-netbsd7-regression-triggered/libglusterfs/src/syncop.c:668
#8  0xbb759b2f in syncenv_processor (thdata=<error reading variable: Cannot access memory at address 0xba0fdfd8>, thdata@entry=<error reading variable: Cannot access memory at address 0xba0fdfd4>)
    at /home/jenkins/root/workspace/rackspace-netbsd7-regression-triggered/libglusterfs/src/syncop.c:699
(gdb) quit

Comment 7 Amar Tumballi 2018-08-29 03:53:45 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.