[Gluster-Maintainers] Build failed in Jenkins: regression-test-burn-in #3012

jenkins at build.gluster.org jenkins at build.gluster.org
Wed Jun 14 08:51:40 UTC 2017 

See <http://build.gluster.org/job/regression-test-burn-in/3012/display/redirect>

------------------------------------------
[...truncated 74.59 KB...]
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
./tests/basic/afr/../../include.rc: line 168: /build/install/sbin/gluster: No such file or directory
find: `/proc/16233': No such file or directory
find: `/proc/16235': No such file or directory
find: `/proc/16250': No such file or directory
find: `/proc/16253': No such file or directory
find: `/proc/16265': 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
Launching heal operation to perform index self heal on volume patchy has been unsuccessful on bricks that are down. Please check if all brick processes are running.
ls: cannot access /d/backends/patchy2: No such file or directory
ls: cannot access /d/backends/patchy2: No such file or directory
diff: /d/backends/patchy0/file1.txt: No such file or directory
diff: /d/backends/patchy2/file1.txt: No such file or directory
./tests/basic/afr/add-brick-self-heal.t .. 
1..34
ok 1, LINENUM:6
ok 2, LINENUM:7
ok 3, LINENUM:8
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: _GFS --attribute-timeout=0 --entry-timeout=0 --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 add-brick patchy replica 3 slave22.cloud.gluster.org:/d/backends/patchy2
not ok 12 , LINENUM:30
FAILED COMMAND: setfattr -n trusted.afr.patchy-client-0 -v 0x000000000000000000000001 /d/backends/patchy2/
not ok 13 , LINENUM:31
FAILED COMMAND: setfattr -n trusted.afr.patchy-client-1 -v 0x000000000000000000000001 /d/backends/patchy2/
not ok 14 Got "" instead of "000000000000000100000001", LINENUM:34
FAILED COMMAND: 000000000000000100000001 get_hex_xattr trusted.afr.patchy-client-2 /d/backends/patchy0
not ok 15 Got "" instead of "000000000000000100000001", LINENUM:35
FAILED COMMAND: 000000000000000100000001 get_hex_xattr trusted.afr.patchy-client-2 /d/backends/patchy1
not ok 16 Got "" instead of "000000000000000000000001", LINENUM:36
FAILED COMMAND: 000000000000000000000001 get_hex_xattr trusted.afr.dirty /d/backends/patchy2
not ok 17 Got "" instead of "1", LINENUM:38
FAILED COMMAND: 1 afr_child_up_status patchy 0
not ok 18 Got "" instead of "1", LINENUM:39
FAILED COMMAND: 1 afr_child_up_status patchy 1
not ok 19 Got "" instead of "1", LINENUM:40
FAILED COMMAND: 1 afr_child_up_status patchy 2
not ok 20 , LINENUM:42
FAILED COMMAND: gluster --mode=script --wignore volume set patchy self-heal-daemon on
not ok 21 Got "" instead of "Y", LINENUM:43
FAILED COMMAND: Y glustershd_up_status
not ok 22 Got "" instead of "1", LINENUM:44
FAILED COMMAND: 1 afr_child_up_status_in_shd patchy 0
not ok 23 Got "" instead of "1", LINENUM:45
FAILED COMMAND: 1 afr_child_up_status_in_shd patchy 1
not ok 24 Got "" instead of "1", LINENUM:46
FAILED COMMAND: 1 afr_child_up_status_in_shd patchy 2
not ok 25 , LINENUM:47
FAILED COMMAND: gluster --mode=script --wignore volume heal patchy
ok 26, LINENUM:50
ok 27, LINENUM:53
ok 28, LINENUM:54
not ok 29 , LINENUM:57
FAILED COMMAND: diff /d/backends/patchy0/file1.txt /d/backends/patchy2/file1.txt
not ok 30 Got "" instead of "qwerty", LINENUM:60
FAILED COMMAND: qwerty get_text_xattr user.test /d/backends/patchy2/file5.txt
not ok 31 Got "" instead of "qwerty", LINENUM:61
FAILED COMMAND: qwerty get_text_xattr user.test /d/backends/patchy0/file5.txt
not ok 32 Got "" instead of "000000000000000000000000", LINENUM:63
FAILED COMMAND: 000000000000000000000000 get_hex_xattr trusted.afr.patchy-client-2 /d/backends/patchy0
not ok 33 Got "" instead of "000000000000000000000000", LINENUM:64
FAILED COMMAND: 000000000000000000000000 get_hex_xattr trusted.afr.patchy-client-2 /d/backends/patchy1
not ok 34 Got "" instead of "000000000000000000000000", LINENUM:65
FAILED COMMAND: 000000000000000000000000 get_hex_xattr trusted.afr.dirty /d/backends/patchy2
Failed 27/34 subtests 

Test Summary Report
-------------------
./tests/basic/afr/add-brick-self-heal.t (Wstat: 0 Tests: 34 Failed: 27)
  Failed tests:  4-9, 11-25, 29-34
Files=1, Tests=34, 221 wallclock secs ( 0.06 usr  0.03 sys +  6.63 cusr 18.47 csys = 25.19 CPU)
Result: FAIL
./tests/basic/afr/add-brick-self-heal.t: bad status 1

       *********************************
       *       REGRESSION FAILED       *
       * Retrying failed tests in case *
       * we got some spurious failures *
       *********************************

volume add-brick: failed: Operation failed
./tests/basic/afr/add-brick-self-heal.t .. 
1..34
ok 1, LINENUM:6
ok 2, LINENUM:7
ok 3, LINENUM:8
ok 4, LINENUM:9
ok 5, LINENUM:10
ok 6, LINENUM:11
ok 7, LINENUM:12
ok 8, LINENUM:14
ok 9, LINENUM:15
ok 10, LINENUM:24
not ok 11 , LINENUM:27
FAILED COMMAND: gluster --mode=script --wignore volume add-brick patchy replica 3 slave22.cloud.gluster.org:/d/backends/patchy2
ok 12, LINENUM:30
ok 13, LINENUM:31
not ok 14 Got "" instead of "000000000000000100000001", LINENUM:34
FAILED COMMAND: 000000000000000100000001 get_hex_xattr trusted.afr.patchy-client-2 /d/backends/patchy0
not ok 15 Got "" instead of "000000000000000100000001", LINENUM:35
FAILED COMMAND: 000000000000000100000001 get_hex_xattr trusted.afr.patchy-client-2 /d/backends/patchy1
not ok 16 Got "" instead of "000000000000000000000001", LINENUM:36
FAILED COMMAND: 000000000000000000000001 get_hex_xattr trusted.afr.dirty /d/backends/patchy2
ok 17, LINENUM:38
ok 18, LINENUM:39
ok 19, LINENUM:40
ok 20, LINENUM:42
ok 21, LINENUM:43
ok 22, LINENUM:44
ok 23, LINENUM:45
ok 24, LINENUM:46
ok 25, LINENUM:47
ok 26, LINENUM:50
ok 27, LINENUM:53
ok 28, LINENUM:54
ok 29, LINENUM:57
ok 30, LINENUM:60
ok 31, LINENUM:61
not ok 32 Got "" instead of "000000000000000000000000", LINENUM:63
FAILED COMMAND: 000000000000000000000000 get_hex_xattr trusted.afr.patchy-client-2 /d/backends/patchy0
not ok 33 Got "" instead of "000000000000000000000000", LINENUM:64
FAILED COMMAND: 000000000000000000000000 get_hex_xattr trusted.afr.patchy-client-2 /d/backends/patchy1
not ok 34 Got "" instead of "000000000000000000000000", LINENUM:65
FAILED COMMAND: 000000000000000000000000 get_hex_xattr trusted.afr.dirty /d/backends/patchy2
Failed 7/34 subtests 

Test Summary Report
-------------------
./tests/basic/afr/add-brick-self-heal.t (Wstat: 0 Tests: 34 Failed: 7)
  Failed tests:  11, 14-16, 32-34
Files=1, Tests=34, 17 wallclock secs ( 0.02 usr  0.01 sys +  2.03 cusr  2.21 csys =  4.27 CPU)
Result: FAIL
End of test ./tests/basic/afr/add-brick-self-heal.t
================================================================================


Run complete
================================================================================
Number of tests found:                             2
Number of tests selected for run based on pattern: 2
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:                     2

1 test(s) failed 
./tests/basic/afr/add-brick-self-heal.t

0 test(s) generated core 


Tests ordered by time taken, slowest to fastest: 
================================================================================
./tests/basic/afr/add-brick-self-heal.t  -  221 second
./tests/basic/0symbol-check.t  -  22 second

Result is 1

tar: Removing leading `/' from member names
Logs archived in http://slave22.cloud.gluster.org/logs/glusterfs-logs-regression-test-burn-in-3012.tgz
kernel.core_pattern = /%e-%p.core
Build step 'Execute shell' marked build as failure
Not sending mail to unregistered user amukherj at redhat.com
Not sending mail to unregistered user avishwan at redhat.com

More information about the maintainers mailing list