[Gluster-Maintainers] Build failed in Jenkins: regression-test-burn-in #3856
jenkins at build.gluster.org
jenkins at build.gluster.org
Thu Feb 15 16:48:54 UTC 2018
See <https://build.gluster.org/job/regression-test-burn-in/3856/display/redirect>
------------------------------------------
[...truncated 256.89 KB...]
sed: read error on /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]
sed: read error on /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]
sed: read error on /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]
sed: read error on /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]
sed: read error on /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]
sed: read error on /var/run/gluster/: Is a directory
rm: cannot remove ‘/var/run/gluster/’: Is a directory
not ok 32 Got "" instead of "4", LINENUM:73
FAILED COMMAND: 4 ec_child_up_count patchy 0
ok 33, LINENUM:76
ok 34, LINENUM:79
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
sed: read error on /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]
sed: read error on /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]
sed: read error on /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]
sed: read error on /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]
sed: read error on /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]
sed: read error on /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]
sed: read error on /var/run/gluster/: Is a directory
rm: cannot remove ‘/var/run/gluster/’: Is a directory
not ok 35 Got "" instead of "6", LINENUM:80
FAILED COMMAND: 6 ec_child_up_count patchy 0
not ok 36 Got "" instead of "^0$", LINENUM:83
FAILED COMMAND: ^0$ get_pending_heal_count patchy
cat: /var/run/gluster/vols/patchy/builder106.cloud.gluster.org-d-backends-patchy3.pid: No such file or directory
Usage: gf_attach uds_path volfile_path (to attach)
gf_attach -d uds_path brick_path (to detach)
ok 37, LINENUM:86
cat: /var/run/gluster/vols/patchy/builder106.cloud.gluster.org-d-backends-patchy4.pid: No such file or directory
Usage: gf_attach uds_path volfile_path (to attach)
gf_attach -d uds_path brick_path (to detach)
ok 38, LINENUM:87
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
sed: read error on /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]
sed: read error on /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]
sed: read error on /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]
sed: read error on /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]
sed: read error on /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]
sed: read error on /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]
sed: read error on /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]
sed: read error on /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]
sed: read error on /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]
sed: read error on /var/run/gluster/: Is a directory
rm: cannot remove ‘/var/run/gluster/’: Is a directory
not ok 39 Got "" instead of "4", LINENUM:88
FAILED COMMAND: 4 ec_child_up_count patchy 0
ok 40, LINENUM:92
Failed 16/40 subtests
Test Summary Report
-------------------
./tests/basic/ec/ec-1468261.t (Wstat: 0 Tests: 40 Failed: 16)
Failed tests: 3-5, 7, 19-23, 25, 27-28, 32, 35-36, 39
Files=1, Tests=40, 257 wallclock secs ( 0.07 usr 0.01 sys + 9.65 cusr 9.77 csys = 19.50 CPU)
Result: FAIL
End of test ./tests/basic/ec/ec-1468261.t
================================================================================
================================================================================
[16:42:55] Running tests in file ./tests/bugs/core/bug-1432542-mpx-restart-crash.t
Timeout set is 300, default 200
./tests/bugs/core/bug-1432542-mpx-restart-crash.t ..
1..105
ok 1, LINENUM:74
ok 2, LINENUM:75
ok 3, LINENUM:50
ok 4, LINENUM:51
ok 5, LINENUM:53
ok 6, LINENUM:56
ok 7, LINENUM:83
ok 8, LINENUM:50
ok 9, LINENUM:51
ok 10, LINENUM:53
ok 11, LINENUM:56
ok 12, LINENUM:83
ok 13, LINENUM:50
ok 14, LINENUM:51
ok 15, LINENUM:53
ok 16, LINENUM:56
ok 17, LINENUM:83
ok 18, LINENUM:50
ok 19, LINENUM:51
ok 20, LINENUM:53
ok 21, LINENUM:56
ok 22, LINENUM:83
ok 23, LINENUM:50
ok 24, LINENUM:51
ok 25, LINENUM:53
ok 26, LINENUM:56
ok 27, LINENUM:83
ok 28, LINENUM:50
ok 29, LINENUM:51
ok 30, LINENUM:53
ok 31, LINENUM:56
ok 32, LINENUM:83
ok 33, LINENUM:50
ok 34, LINENUM:51
ok 35, LINENUM:53
ok 36, LINENUM:56
ok 37, LINENUM:83
ok 38, LINENUM:50
ok 39, LINENUM:51
ok 40, LINENUM:53
ok 41, LINENUM:56
ok 42, LINENUM:83
ok 43, LINENUM:50
ok 44, LINENUM:51
ok 45, LINENUM:53
ok 46, LINENUM:56
ok 47, LINENUM:83
ok 48, LINENUM:50
ok 49, LINENUM:51
ok 50, LINENUM:53
ok 51, LINENUM:56
ok 52, LINENUM:83
ok 53, LINENUM:50
ok 54, LINENUM:51
ok 55, LINENUM:53
ok 56, LINENUM:56
ok 57, LINENUM:83
ok 58, LINENUM:50
ok 59, LINENUM:51
ok 60, LINENUM:53
ok 61, LINENUM:56
ok 62, LINENUM:83
ok 63, LINENUM:50
ok 64, LINENUM:51
ok 65, LINENUM:53
ok 66, LINENUM:56
ok 67, LINENUM:83
ok 68, LINENUM:50
ok 69, LINENUM:51
ok 70, LINENUM:53
ok 71, LINENUM:56
ok 72, LINENUM:83
ok 73, LINENUM:50
ok 74, LINENUM:51
ok 75, LINENUM:53
ok 76, LINENUM:56
ok 77, LINENUM:83
ok 78, LINENUM:50
ok 79, LINENUM:51
ok 80, LINENUM:53
ok 81, LINENUM:56
ok 82, LINENUM:83
ok 83, LINENUM:50
ok 84, LINENUM:51
ok 85, LINENUM:53
ok 86, LINENUM:56
ok 87, LINENUM:83
ok 88, LINENUM:50
ok 89, LINENUM:51
ok 90, LINENUM:53
ok 91, LINENUM:56
ok 92, LINENUM:83
ok 93, LINENUM:50
ok 94, LINENUM:51
ok 95, LINENUM:53
ok 96, LINENUM:56
ok 97, LINENUM:83
ok 98, LINENUM:50
ok 99, LINENUM:51
ok 100, LINENUM:53
ok 101, LINENUM:56
ok 102, LINENUM:83
ok 103, LINENUM:87
ok 104, LINENUM:89
ok 105, LINENUM:95
ok
All tests successful.
Files=1, Tests=105, 231 wallclock secs ( 0.06 usr 0.00 sys + 11.77 cusr 7.12 csys = 18.95 CPU)
Result: PASS
End of test ./tests/bugs/core/bug-1432542-mpx-restart-crash.t
================================================================================
Run complete
================================================================================
Number of tests found: 607
Number of tests selected for run based on pattern: 3
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: 3
Tests ordered by time taken, slowest to fastest:
================================================================================
./tests/basic/ec/ec-1468261.t - 300 second
./tests/basic/afr/lk-quorum.t - 300 second
./tests/bugs/core/bug-1432542-mpx-restart-crash.t - 231 second
2 test(s) failed
./tests/basic/afr/lk-quorum.t
./tests/basic/ec/ec-1468261.t
0 test(s) generated core
2 test(s) needed retry
./tests/basic/afr/lk-quorum.t
./tests/basic/ec/ec-1468261.t
Result is 1
tar: Removing leading `/' from member names
ssh: connect to host http.int.rht.gluster.org port 22: Connection timed out
lost connection
kernel.core_pattern = /%e-%p.core
Build step 'Execute shell' marked build as failure
More information about the maintainers
mailing list