[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-fedora-29 #542
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-29/542/display/redirect> ------------------------------------------ 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-fedora-29 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-29/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins8593959852793507990.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_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, 25 wallclock secs ( 0.44 usr 0.10 sys + 8.16 cusr 0.78 csys = 9.48 CPU) Result: FAIL Failed 1/12 test programs. 1/1943 subtests failed. Build step 'Execute shell' marked build as failure
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-29/543/display/redirect> ------------------------------------------ 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-fedora-29 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-29/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins1414377992090927878.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_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, 31 wallclock secs ( 0.40 usr 0.06 sys + 8.40 cusr 0.60 csys = 9.46 CPU) Result: FAIL Failed 1/12 test programs. 1/1943 subtests failed. Build step 'Execute shell' marked build as failure
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-29/544/display/redirect> ------------------------------------------ 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-fedora-29 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-29/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins13314081133736494586.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_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, 31 wallclock secs ( 0.41 usr 0.07 sys + 8.23 cusr 0.56 csys = 9.27 CPU) Result: FAIL Failed 1/12 test programs. 1/1944 subtests failed. Build step 'Execute shell' marked build as failure
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-29/545/display/redirect> ------------------------------------------ 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-fedora-29 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-29/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins3058249214490301218.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_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, 27 wallclock secs ( 0.37 usr 0.07 sys + 8.54 cusr 0.62 csys = 9.60 CPU) Result: FAIL Failed 1/12 test programs. 1/1944 subtests failed. Build step 'Execute shell' marked build as failure
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-29/546/display/redirect> ------------------------------------------ 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-fedora-29 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-29/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins4886388096503644328.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_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, 36 wallclock secs ( 0.42 usr 0.05 sys + 8.65 cusr 0.58 csys = 9.70 CPU) Result: FAIL Failed 1/12 test programs. 1/1944 subtests failed. Build step 'Execute shell' marked build as failure
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-29/547/display/redirect> ------------------------------------------ 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-fedora-29 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-29/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins2415430520415223789.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_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, 59 wallclock secs ( 0.41 usr 0.06 sys + 8.73 cusr 0.56 csys = 9.76 CPU) Result: FAIL Failed 1/12 test programs. 1/1944 subtests failed. Build step 'Execute shell' marked build as failure
participants (1)
-
ci＠centos.org