See <http://build.gluster.org/job/regression-test-burn-in/1578/>
------------------------------------------ [...truncated 2600 lines...] ok 16, LINENUM:29 ok 17, LINENUM:32 ok 18, LINENUM:33 ok 19, LINENUM:34 ok 20, LINENUM:35 ok All tests successful. Files=1, Tests=20, 12 wallclock secs ( 0.02 usr 0.01 sys + 1.84 cusr 1.57 csys = 3.44 CPU) Result: PASS End of test ./tests/basic/afr/read-subvol-entry.t ================================================================================ ================================================================================ [00:05:26] Running tests in file ./tests/basic/afr/replace-brick-self-heal.t setfattr: /d/backends/patchy1_new/: No such file or directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] grep: /var/run/gluster/: Is a directory rm: cannot remove `/var/run/gluster/': Is a directory ls: cannot access /d/backends/patchy0: No such file or directory ls: cannot access /d/backends/patchy1_new: No such file or directory ls: cannot access /d/backends/patchy0: No such file or directory ls: cannot access /d/backends/patchy1: No such file or directory diff: /d/backends/patchy0/file1.txt: No such file or directory diff: /d/backends/patchy1_new/file1.txt: No such file or directory diff: /d/backends/patchy0/file1.txt: No such file or directory diff: /d/backends/patchy1/file1.txt: No such file or directory ./tests/basic/afr/replace-brick-self-heal.t .. 1..29 not ok 1 , LINENUM:6 FAILED COMMAND: glusterd ok 2, LINENUM:7 not ok 3 , LINENUM:8 FAILED COMMAND: gluster --mode=script --wignore volume create patchy replica 2 slave22.cloud.gluster.org:/d/backends/patchy0 slave22.cloud.gluster.org:/d/backends/patchy1 not ok 4 , LINENUM:9 FAILED COMMAND: gluster --mode=script --wignore volume start patchy not ok 5 , LINENUM:10 FAILED COMMAND: gluster --mode=script --wignore volume set patchy cluster.data-self-heal off not ok 6 , LINENUM:11 FAILED COMMAND: gluster --mode=script --wignore volume set patchy cluster.metadata-self-heal off not ok 7 , LINENUM:12 FAILED COMMAND: gluster --mode=script --wignore volume set patchy cluster.entry-self-heal off not ok 8 , LINENUM:14 FAILED COMMAND: gluster --mode=script --wignore volume set patchy self-heal-daemon off not ok 9 , LINENUM:15 FAILED COMMAND: glusterfs --volfile-id=patchy --volfile-server=slave22.cloud.gluster.org /mnt/glusterfs/0 ok 10, LINENUM:24 not ok 11 , LINENUM:27 FAILED COMMAND: gluster --mode=script --wignore volume replace-brick patchy slave22.cloud.gluster.org:/d/backends/patchy1 slave22.cloud.gluster.org:/d/backends/patchy1_new commit force not ok 12 , LINENUM:30 FAILED COMMAND: setfattr -n trusted.afr.patchy-client-0 -v 0x000000000000000000000001 /d/backends/patchy1_new/ not ok 13 Got "" instead of "000000000000000100000001", LINENUM:33 FAILED COMMAND: 000000000000000100000001 get_hex_xattr trusted.afr.patchy-client-1 /d/backends/patchy0 not ok 14 Got "" instead of "000000000000000000000001", LINENUM:34 FAILED COMMAND: 000000000000000000000001 get_hex_xattr trusted.afr.dirty /d/backends/patchy1_new not ok 15 Got "" instead of "1", LINENUM:36 FAILED COMMAND: 1 afr_child_up_status patchy 0 not ok 16 Got "" instead of "1", LINENUM:37 FAILED COMMAND: 1 afr_child_up_status patchy 1 not ok 17 , LINENUM:39 FAILED COMMAND: gluster --mode=script --wignore volume set patchy self-heal-daemon on not ok 18 Got "" instead of "Y", LINENUM:40 FAILED COMMAND: Y glustershd_up_status not ok 19 Got "" instead of "1", LINENUM:41 FAILED COMMAND: 1 afr_child_up_status_in_shd patchy 0 not ok 20 Got "" instead of "1", LINENUM:42 FAILED COMMAND: 1 afr_child_up_status_in_shd patchy 1 not ok 21 , LINENUM:43 FAILED COMMAND: gluster --mode=script --wignore volume heal patchy not ok 22 Got "" instead of "0", LINENUM:46 FAILED COMMAND: 0 get_pending_heal_count patchy ok 23, LINENUM:49 ok 24, LINENUM:52 not ok 25 Got "" instead of "000000000000000000000000", LINENUM:53 FAILED COMMAND: 000000000000000000000000 get_hex_xattr trusted.afr.patchy-client-1 /d/backends/patchy0 not ok 26 , LINENUM:56 FAILED COMMAND: diff /d/backends/patchy0/file1.txt /d/backends/patchy1_new/file1.txt not ok 27 , LINENUM:58 FAILED COMMAND: diff /d/backends/patchy0/file1.txt /d/backends/patchy1/file1.txt not ok 28 Got "" instead of "qwerty", LINENUM:61 FAILED COMMAND: qwerty get_text_xattr user.test /d/backends/patchy1_new/file5.txt not ok 29 Got "" instead of "qwerty", LINENUM:62 FAILED COMMAND: qwerty get_text_xattr user.test /d/backends/patchy0/file5.txt Failed 25/29 subtests Test Summary Report ------------------- ./tests/basic/afr/replace-brick-self-heal.t (Wstat: 0 Tests: 29 Failed: 25) Failed tests: 1, 3-9, 11-22, 25-29 Files=1, Tests=29, 183 wallclock secs ( 0.04 usr 0.02 sys + 18.93 cusr 12.19 csys = 31.18 CPU) Result: FAIL End of test ./tests/basic/afr/replace-brick-self-heal.t ================================================================================ Run complete ================================================================================ Number of tests found: 26 Number of tests selected for run based on pattern: 26 Number of tests skipped as they were marked bad: 0 Number of tests skipped because of known_issues: 0 Number of tests that were run: 26 1 test(s) failed ./tests/basic/afr/replace-brick-self-heal.t 0 test(s) generated core Tests ordered by time taken, slowest to fastest: ================================================================================ ./tests/basic/afr/entry-self-heal.t - 208 second ./tests/basic/afr/replace-brick-self-heal.t - 183 second ./tests/basic/afr/granular-esh/conservative-merge.t - 114 second ./tests/basic/afr/granular-esh/granular-esh.t - 102 second ./tests/basic/afr/granular-esh/add-brick.t - 99 second ./tests/basic/afr/add-brick-self-heal.t - 99 second ./tests/basic/afr/metadata-self-heal.t - 81 second ./tests/basic/afr/arbiter.t - 41 second ./tests/basic/afr/data-self-heal.t - 40 second ./tests/basic/afr/quorum.t - 36 second ./tests/basic/afr/durability-off.t - 27 second ./tests/basic/afr/arbiter-add-brick.t - 25 second ./tests/basic/afr/heal-quota.t - 24 second ./tests/basic/afr/gfid-self-heal.t - 23 second ./tests/basic/0symbol-check.t - 22 second ./tests/basic/afr/granular-esh/replace-brick.t - 21 second ./tests/basic/afr/client-side-heal.t - 18 second ./tests/basic/afr/read-subvol-data.t - 15 second ./tests/basic/afr/arbiter-mount.t - 13 second ./tests/basic/afr/read-subvol-entry.t - 12 second ./tests/basic/afr/heal-info.t - 12 second ./tests/basic/afr/arbiter-remove-brick.t - 12 second ./tests/basic/afr/gfid-heal.t - 11 second ./tests/basic/afr/gfid-mismatch.t - 10 second ./tests/basic/afr/arbiter-statfs.t - 10 second ./tests/basic/afr/arbiter-cli.t - 7 second Result is 1 tar: Removing leading `/' from member names Logs archived in http://slave22.cloud.gluster.org/logs/glusterfs-logs-20160824:23:47:20.tgz kernel.core_pattern = /%e-%p.core Build step 'Execute shell' marked build as failure _______________________________________________ maintainers mailing list [email protected] http://www.gluster.org/mailman/listinfo/maintainers
