On 08/13/2018 06:12 AM, Shyam Ranganathan wrote:
As a means of keeping the focus going and squashing the remaining tests
that were failing sporadically, request each test/component owner to,
- respond to this mail changing the subject (testname.t) to the test
name that they are responding to (adding more than one in case they have
the same RCA)
- with the current RCA and status of the same
List of tests and current owners as per the spreadsheet that we were
tracking are:
TBD
./tests/bugs/glusterd/remove-brick-testcases.t TBD
In this case, the .t passed but self-heal-daemon (which btw does not
have any role in this test because there is no I/O or heals in this .t)
has crashed with the following bt:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007ff8c6bc0b4f in _IO_cleanup () from ./lib64/libc.so.6
[Current thread is 1 (LWP 17530)]
(gdb)
(gdb) bt
#0 0x00007ff8c6bc0b4f in _IO_cleanup () from ./lib64/libc.so.6
#1 0x00007ff8c6b7cb8b in __run_exit_handlers () from ./lib64/libc.so.6
#2 0x00007ff8c6b7cc27 in exit () from ./lib64/libc.so.6
#3 0x000000000040b14d in cleanup_and_exit (signum=15) at glusterfsd.c:1570
#4 0x000000000040de71 in glusterfs_sigwaiter (arg=0x7ffd5f270d20) at
glusterfsd.c:2332
#5 0x00007ff8c757ce25 in start_thread () from ./lib64/libpthread.so.0
#6 0x00007ff8c6c41bad in clone () from ./lib64/libc.so.6
Not able to find out the reason of the crash. Any pointers are
appreciated. Regression run/core can be found at
https://build.gluster.org/job/line-coverage/432/consoleFull .
Thanks,
Ravi
_______________________________________________
Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel
