Build failed in Jenkins: libvirt-perl-check » libvirt-freebsd-11 #998
by ci＠centos.org
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-11/9...>
------------------------------------------
Started by upstream project "libvirt-perl-check" build number 998
originally caused by:
Started by upstream project "libvirt-perl-build" build number 1000
originally caused by:
Started by upstream project "libvirt-build" build number 1168
originally caused by:
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on libvirt-freebsd-11 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-11/ws/>
[libvirt-perl] $ /bin/sh -xe /tmp/jenkins9972092734623346822.sh
+ export 'TEST_MAINTAINER=1'
+ perl Build test
t/005-pod.t ............ ok
t/010-pod-coverage.t ... ok
t/015-changes.t ........ ok
t/020-constants.t ...... ok
# Failed test 'VIR_DOMAIN_EVENT_CRASHED_CRASHLOADED'
# at t/030-api-coverage.t line 175.
# Looks like you failed 1 test of 1754.
t/030-api-coverage.t ...
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1754 subtests
t/100-connect.t ........ ok
t/200-domains.t ........ ok
t/300-networks.t ....... ok
t/400-storage-pools.t .. ok
t/500-storage-vols.t ... ok
t/600-interfaces.t ..... ok
t/800-events.t ......... ok
Test Summary Report
-------------------
t/030-api-coverage.t (Wstat: 256 Tests: 1754 Failed: 1)
Failed test: 750
Non-zero exit status: 1
Files=12, Tests=2012, 46 wallclock secs ( 0.88 usr 0.54 sys + 19.89 cusr 1.78 csys = 23.09 CPU)
Result: FAIL
Failed 1/12 test programs. 1/2012 subtests failed.
Build step 'Execute shell' marked build as failure
4 years, 8 months
Build failed in Jenkins: libvirt-perl-check » libvirt-fedora-30 #998
by ci＠centos.org
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-30/99...>
------------------------------------------
Started by upstream project "libvirt-perl-check" build number 998
originally caused by:
Started by upstream project "libvirt-perl-build" build number 1000
originally caused by:
Started by upstream project "libvirt-build" build number 1168
originally caused by:
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on libvirt-fedora-30 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-30/ws/>
[libvirt-perl] $ /bin/sh -xe /tmp/jenkins4057768491292937599.sh
+ export TEST_MAINTAINER=1
+ TEST_MAINTAINER=1
+ perl Build test
t/005-pod.t ............ ok
t/010-pod-coverage.t ... ok
t/015-changes.t ........ ok
t/020-constants.t ...... ok
# Failed test 'VIR_DOMAIN_EVENT_CRASHED_CRASHLOADED'
# at t/030-api-coverage.t line 175.
# Looks like you failed 1 test of 1754.
t/030-api-coverage.t ...
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1754 subtests
t/100-connect.t ........ ok
t/200-domains.t ........ ok
t/300-networks.t ....... ok
t/400-storage-pools.t .. ok
t/500-storage-vols.t ... ok
t/600-interfaces.t ..... ok
t/800-events.t ......... ok
Test Summary Report
-------------------
t/030-api-coverage.t (Wstat: 256 Tests: 1754 Failed: 1)
Failed test: 750
Non-zero exit status: 1
Files=12, Tests=2012, 41 wallclock secs ( 0.42 usr 0.07 sys + 8.98 cusr 0.69 csys = 10.16 CPU)
Result: FAIL
Failed 1/12 test programs. 1/2012 subtests failed.
Build step 'Execute shell' marked build as failure
4 years, 8 months
Build failed in Jenkins: libvirt-perl-check » libvirt-freebsd-12 #998
by ci＠centos.org
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-12/9...>
------------------------------------------
Started by upstream project "libvirt-perl-check" build number 998
originally caused by:
Started by upstream project "libvirt-perl-build" build number 1000
originally caused by:
Started by upstream project "libvirt-build" build number 1168
originally caused by:
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on libvirt-freebsd-12 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-12/ws/>
[libvirt-perl] $ /bin/sh -xe /tmp/jenkins15968333646139382948.sh
+ export 'TEST_MAINTAINER=1'
+ perl Build test
t/005-pod.t ............ ok
t/010-pod-coverage.t ... ok
t/015-changes.t ........ ok
t/020-constants.t ...... ok
# Failed test 'VIR_DOMAIN_EVENT_CRASHED_CRASHLOADED'
# at t/030-api-coverage.t line 175.
# Looks like you failed 1 test of 1754.
t/030-api-coverage.t ...
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1754 subtests
t/100-connect.t ........ ok
t/200-domains.t ........ ok
t/300-networks.t ....... ok
t/400-storage-pools.t .. ok
t/500-storage-vols.t ... ok
t/600-interfaces.t ..... ok
t/800-events.t ......... ok
Test Summary Report
-------------------
t/030-api-coverage.t (Wstat: 256 Tests: 1754 Failed: 1)
Failed test: 750
Non-zero exit status: 1
Files=12, Tests=2012, 50 wallclock secs ( 0.91 usr 0.70 sys + 18.90 cusr 1.97 csys = 22.47 CPU)
Result: FAIL
Failed 1/12 test programs. 1/2012 subtests failed.
Build step 'Execute shell' marked build as failure
4 years, 8 months
Build failed in Jenkins: libvirt-perl-check » libvirt-fedora-rawhide #998
by ci＠centos.org
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-rawhi...>
------------------------------------------
Started by upstream project "libvirt-perl-check" build number 998
originally caused by:
Started by upstream project "libvirt-perl-build" build number 1000
originally caused by:
Started by upstream project "libvirt-build" build number 1168
originally caused by:
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on libvirt-fedora-rawhide (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-rawhi...>
[libvirt-perl] $ /bin/sh -xe /tmp/jenkins17694628221700222522.sh
+ export TEST_MAINTAINER=1
+ TEST_MAINTAINER=1
+ perl Build test
t/005-pod.t ............ ok
t/010-pod-coverage.t ... ok
t/015-changes.t ........ ok
t/020-constants.t ...... ok
# Failed test 'VIR_DOMAIN_EVENT_CRASHED_CRASHLOADED'
# at t/030-api-coverage.t line 175.
# Looks like you failed 1 test of 1754.
t/030-api-coverage.t ...
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1754 subtests
t/100-connect.t ........ ok
t/200-domains.t ........ ok
t/300-networks.t ....... ok
t/400-storage-pools.t .. ok
t/500-storage-vols.t ... ok
t/600-interfaces.t ..... ok
t/800-events.t ......... ok
Test Summary Report
-------------------
t/030-api-coverage.t (Wstat: 256 Tests: 1754 Failed: 1)
Failed test: 750
Non-zero exit status: 1
Files=12, Tests=2012, 89 wallclock secs ( 0.50 usr 0.07 sys + 9.08 cusr 0.72 csys = 10.37 CPU)
Result: FAIL
Failed 1/12 test programs. 1/2012 subtests failed.
Build step 'Execute shell' marked build as failure
4 years, 8 months
Build failed in Jenkins: libvirt-perl-check » libvirt-fedora-31 #998
by ci＠centos.org
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-31/99...>
------------------------------------------
Started by upstream project "libvirt-perl-check" build number 998
originally caused by:
Started by upstream project "libvirt-perl-build" build number 1000
originally caused by:
Started by upstream project "libvirt-build" build number 1168
originally caused by:
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on libvirt-fedora-31 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-31/ws/>
[libvirt-perl] $ /bin/sh -xe /tmp/jenkins1110895124204072636.sh
+ export TEST_MAINTAINER=1
+ TEST_MAINTAINER=1
+ perl Build test
t/005-pod.t ............ ok
t/010-pod-coverage.t ... ok
t/015-changes.t ........ ok
t/020-constants.t ...... ok
# Failed test 'VIR_DOMAIN_EVENT_CRASHED_CRASHLOADED'
# at t/030-api-coverage.t line 175.
# Looks like you failed 1 test of 1754.
t/030-api-coverage.t ...
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1754 subtests
t/100-connect.t ........ ok
t/200-domains.t ........ ok
t/300-networks.t ....... ok
t/400-storage-pools.t .. ok
t/500-storage-vols.t ... ok
t/600-interfaces.t ..... ok
t/800-events.t ......... ok
Test Summary Report
-------------------
t/030-api-coverage.t (Wstat: 256 Tests: 1754 Failed: 1)
Failed test: 750
Non-zero exit status: 1
Files=12, Tests=2012, 76 wallclock secs ( 0.53 usr 0.07 sys + 9.20 cusr 0.70 csys = 10.50 CPU)
Result: FAIL
Failed 1/12 test programs. 1/2012 subtests failed.
Build step 'Execute shell' marked build as failure
4 years, 8 months
Build failed in Jenkins: libvirt-perl-check » libvirt-centos-7 #998
by ci＠centos.org
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-centos-7/998...>
------------------------------------------
Started by upstream project "libvirt-perl-check" build number 998
originally caused by:
Started by upstream project "libvirt-perl-build" build number 1000
originally caused by:
Started by upstream project "libvirt-build" build number 1168
originally caused by:
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on libvirt-centos-7 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-centos-7/ws/>
[libvirt-perl] $ /bin/sh -xe /tmp/jenkins4919687577180138398.sh
+ export TEST_MAINTAINER=1
+ TEST_MAINTAINER=1
+ perl Build test
t/005-pod.t ............ ok
t/010-pod-coverage.t ... ok
t/015-changes.t ........ ok
t/020-constants.t ...... ok
# Failed test 'VIR_DOMAIN_EVENT_CRASHED_CRASHLOADED'
# at t/030-api-coverage.t line 175.
# Looks like you failed 1 test of 1754.
t/030-api-coverage.t ...
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1754 subtests
t/100-connect.t ........ ok
t/200-domains.t ........ ok
t/300-networks.t ....... ok
t/400-storage-pools.t .. ok
t/500-storage-vols.t ... ok
t/600-interfaces.t ..... ok
t/800-events.t ......... ok
Test Summary Report
-------------------
t/030-api-coverage.t (Wstat: 256 Tests: 1754 Failed: 1)
Failed test: 750
Non-zero exit status: 1
Files=12, Tests=2012, 38 wallclock secs ( 0.44 usr 0.05 sys + 8.50 cusr 0.42 csys = 9.41 CPU)
Result: FAIL
Failed 1/12 test programs. 1/2012 subtests failed.
Build step 'Execute shell' marked build as failure
4 years, 8 months