10:37 a.m.
See
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-debian-9/542...
------------------------------------------
Started by upstream project "libvirt-perl-check" build number 542
originally caused by:
Started by upstream project "libvirt-perl-build" build number 543
originally caused by:
Started by upstream project "libvirt-build" build number 651
originally caused by:
Started by an SCM change
Started by an SCM change
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on libvirt-debian-9 (libvirt) in workspace
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-debian-9/ws/...
[libvirt-perl] $ /bin/sh -xe /tmp/jenkins3625465712218787751.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_SNAPSHOT_CREATE_VALIDATE'
# at t/030-api-coverage.t line 175.
# Looks like you failed 1 test of 1687.
t/030-api-coverage.t ...
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1687 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: 1687 Failed: 1)
Failed test: 1039
Non-zero exit status: 1
Files=12, Tests=1943, 14 wallclock secs ( 0.64 usr 0.09 sys + 12.13 cusr 0.56 csys =
13.42 CPU)
Result: FAIL
Failed 1/12 test programs. 1/1943 subtests failed.
Build step 'Execute shell' marked build as failure
11:58 a.m.
New subject: [Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-debian-9 #543
See
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-debian-9/543...
------------------------------------------
Started by upstream project "libvirt-perl-check" build number 543
originally caused by:
Started by upstream project "libvirt-perl-build" build number 544
originally caused by:
Started by upstream project "libvirt-build" build number 652
originally caused by:
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on libvirt-debian-9 (libvirt) in workspace
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-debian-9/ws/...
[libvirt-perl] $ /bin/sh -xe /tmp/jenkins7050237048856645581.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_SNAPSHOT_CREATE_VALIDATE'
# at t/030-api-coverage.t line 175.
# Looks like you failed 1 test of 1687.
t/030-api-coverage.t ...
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1687 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: 1687 Failed: 1)
Failed test: 1039
Non-zero exit status: 1
Files=12, Tests=1943, 20 wallclock secs ( 0.78 usr 0.10 sys + 10.76 cusr 0.52 csys =
12.16 CPU)
Result: FAIL
Failed 1/12 test programs. 1/1943 subtests failed.
Build step 'Execute shell' marked build as failure
7:42 a.m.
New subject: [Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-debian-9 #544
See
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-debian-9/544...
------------------------------------------
Started by upstream project "libvirt-perl-check" build number 544
originally caused by:
Started by upstream project "libvirt-perl-build" build number 545
originally caused by:
Started by an SCM change
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on libvirt-debian-9 (libvirt) in workspace
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-debian-9/ws/...
[libvirt-perl] $ /bin/sh -xe /tmp/jenkins8755206451106379232.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_CONNECT_LIST_STORAGE_POOLS_ISCSI_DIRECT'
# at t/030-api-coverage.t line 175.
# Looks like you failed 1 test of 1688.
t/030-api-coverage.t ...
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1688 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: 1688 Failed: 1)
Failed test: 606
Non-zero exit status: 1
Files=12, Tests=1944, 50 wallclock secs ( 0.64 usr 0.10 sys + 13.23 cusr 0.74 csys =
14.71 CPU)
Result: FAIL
Failed 1/12 test programs. 1/1944 subtests failed.
Build step 'Execute shell' marked build as failure
8:12 a.m.
New subject: [Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-debian-9 #545
See
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-debian-9/545...
------------------------------------------
Started by upstream project "libvirt-perl-check" build number 545
originally caused by:
Started by upstream project "libvirt-perl-build" build number 546
originally caused by:
Started by upstream project "libvirt-build" build number 655
originally caused by:
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on libvirt-debian-9 (libvirt) in workspace
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-debian-9/ws/...
[libvirt-perl] $ /bin/sh -xe /tmp/jenkins2502945194174850320.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_CONNECT_LIST_STORAGE_POOLS_ISCSI_DIRECT'
# at t/030-api-coverage.t line 175.
# Looks like you failed 1 test of 1688.
t/030-api-coverage.t ...
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1688 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: 1688 Failed: 1)
Failed test: 606
Non-zero exit status: 1
Files=12, Tests=1944, 15 wallclock secs ( 0.49 usr 0.14 sys + 11.36 cusr 0.71 csys =
12.70 CPU)
Result: FAIL
Failed 1/12 test programs. 1/1944 subtests failed.
Build step 'Execute shell' marked build as failure
9:07 a.m.
New subject: [Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-debian-9 #546
See
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-debian-9/546...
------------------------------------------
Started by upstream project "libvirt-perl-check" build number 546
originally caused by:
Started by upstream project "libvirt-perl-build" build number 547
originally caused by:
Started by upstream project "libvirt-build" build number 656
originally caused by:
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on libvirt-debian-9 (libvirt) in workspace
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-debian-9/ws/...
[libvirt-perl] $ /bin/sh -xe /tmp/jenkins2277909367235319072.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_CONNECT_LIST_STORAGE_POOLS_ISCSI_DIRECT'
# at t/030-api-coverage.t line 175.
# Looks like you failed 1 test of 1688.
t/030-api-coverage.t ...
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1688 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: 1688 Failed: 1)
Failed test: 606
Non-zero exit status: 1
Files=12, Tests=1944, 24 wallclock secs ( 0.78 usr 0.08 sys + 14.35 cusr 0.69 csys =
15.90 CPU)
Result: FAIL
Failed 1/12 test programs. 1/1944 subtests failed.
Build step 'Execute shell' marked build as failure
10:15 a.m.
New subject: [Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-debian-9 #547
See
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-debian-9/547...
------------------------------------------
Started by upstream project "libvirt-perl-check" build number 547
originally caused by:
Started by upstream project "libvirt-perl-build" build number 548
originally caused by:
Started by upstream project "libvirt-build" build number 657
originally caused by:
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on libvirt-debian-9 (libvirt) in workspace
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-debian-9/ws/...
[libvirt-perl] $ /bin/sh -xe /tmp/jenkins8121370670330707272.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_CONNECT_LIST_STORAGE_POOLS_ISCSI_DIRECT'
# at t/030-api-coverage.t line 175.
# Looks like you failed 1 test of 1688.
t/030-api-coverage.t ...
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1688 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: 1688 Failed: 1)
Failed test: 606
Non-zero exit status: 1
Files=12, Tests=1944, 60 wallclock secs ( 0.75 usr 0.10 sys + 13.94 cusr 0.70 csys =
15.49 CPU)
Result: FAIL
Failed 1/12 test programs. 1/1944 subtests failed.
Build step 'Execute shell' marked build as failure
11:23 a.m.
New subject: [Libvirt-ci] Jenkins build is back to normal : libvirt-perl-check » libvirt-debian-9 #548
1987
days inactive
1991
days old
6 comments
1 participants
participants (1)
-
ci＠centos.org