Description of problem: ---------------------------- Test ./tests/features/ipc.t is fails on executing ./tests/features/ipctest.py Script received signal SIGSEGV, Segmentation Error (Core Dumb) in __GLFS_ENTRY_VALIDATE_FS (fs, invalid_fs); at glfs.c: Version-Release number of selected component (if applicable): 3.10.7 ---------------------------- How reproducible: ---------------------------- Build and install glusterfs on System Z (s390x) run ./tests/features/ipc.t testcase Version-Release number of selected component (if applicable): ---------------------------- Steps to Reproduce: ---------------------------- 1. git clone https://github.com/gluster/glusterfs && cd glusterfs 2. git checkout v3.10.7 3. ./autogen.sh 4. ./configure 5. make 6. make install 7. ./run-tests.sh ./tests/features/ipc.t ---------------------------- Actual results: ---------------------------- Failed 1/6 subtests Test Summary Report ------------------- ./tests/features/ipc.t (Wstat: 0 Tests: 6 Failed: 1) Failed test: 6 Files=1, Tests=6, 3 wallclock secs ( 0.03 usr 0.00 sys + 0.50 cusr 0.34 csys = 0.87 CPU) Result: FAIL ./tests/features/ipc.t: bad status 1 ********************************* * REGRESSION FAILED * * Retrying failed tests in case * * we got some spurous failures * ********************************* ---------------------------- Expected results: ---------------------------- ok All tests successful. Files=1, Tests=78, 45 wallclock secs ( 0.14 usr 0.03 sys + 9.27 cusr 4.64 csys = 14.08 CPU) Result: PASS ---------------------------- Additional info: ---------------------------- Thread 1 "python" received signal SIGSEGV, Segmentation fault. 0x000003fffd89c8e4 in pub_glfs_set_volfile_server (fs=0x33f110, transport=0x3fffdc2466c "tcp", host=0x3fffdc126e4 "73da538ef028", port=<optimized out>) at glfs.c:425 425 __GLFS_ENTRY_VALIDATE_FS (fs, invalid_fs);
*** Bug 1511373 has been marked as a duplicate of this bug. ***
This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained. As a result this bug is being closed. If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately.