[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-freebsd-12 #840
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-12/840/display/redirect> ------------------------------------------ [...truncated 20.65 KB...] Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started 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-freebsd-12 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-12/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins10696268146146179162.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 'virDomainAgentSetResponseTimeout' # at t/030-api-coverage.t line 161. # Failed test 'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_BLOCK' # at t/030-api-coverage.t line 175. # Failed test 'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_DEFAULT' # at t/030-api-coverage.t line 175. # Failed test 'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_NOWAIT' # at t/030-api-coverage.t line 175. # Failed test 'VIR_FROM_BPF' # at t/030-api-coverage.t line 175. # Looks like you failed 5 tests of 1739. t/030-api-coverage.t ... Dubious, test returned 5 (wstat 1280, 0x500) Failed 5/1739 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: 1280 Tests: 1739 Failed: 5) Failed tests: 113, 655-657, 1248 Non-zero exit status: 5 Files=12, Tests=1997, 58 wallclock secs ( 1.02 usr 0.41 sys + 20.30 cusr 2.03 csys = 23.76 CPU) Result: FAIL Failed 1/12 test programs. 5/1997 subtests failed. Build step 'Execute shell' marked build as failure
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-12/841/display/redirect> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 841 originally caused by: Started by upstream project "libvirt-perl-build" build number 842 originally caused by: Started by upstream project "libvirt-build" build number 986 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/jenkins2897856886563552284.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 'virDomainAgentSetResponseTimeout' # at t/030-api-coverage.t line 161. # Failed test 'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_BLOCK' # at t/030-api-coverage.t line 175. # Failed test 'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_DEFAULT' # at t/030-api-coverage.t line 175. # Failed test 'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_NOWAIT' # at t/030-api-coverage.t line 175. # Failed test 'VIR_FROM_BPF' # at t/030-api-coverage.t line 175. # Looks like you failed 5 tests of 1739. t/030-api-coverage.t ... Dubious, test returned 5 (wstat 1280, 0x500) Failed 5/1739 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: 1280 Tests: 1739 Failed: 5) Failed tests: 113, 655-657, 1248 Non-zero exit status: 5 Files=12, Tests=1997, 52 wallclock secs ( 0.85 usr 0.35 sys + 18.02 cusr 2.03 csys = 21.26 CPU) Result: FAIL Failed 1/12 test programs. 5/1997 subtests failed. Build step 'Execute shell' marked build as failure
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-12/842/display/redirect> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 842 originally caused by: Started by upstream project "libvirt-perl-build" build number 843 originally caused by: Started by upstream project "libvirt-build" build number 987 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/jenkins12036146432008255439.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 'virDomainAgentSetResponseTimeout' # at t/030-api-coverage.t line 161. # Failed test 'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_BLOCK' # at t/030-api-coverage.t line 175. # Failed test 'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_DEFAULT' # at t/030-api-coverage.t line 175. # Failed test 'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_NOWAIT' # at t/030-api-coverage.t line 175. # Failed test 'VIR_FROM_BPF' # at t/030-api-coverage.t line 175. # Looks like you failed 5 tests of 1739. t/030-api-coverage.t ... Dubious, test returned 5 (wstat 1280, 0x500) Failed 5/1739 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: 1280 Tests: 1739 Failed: 5) Failed tests: 113, 655-657, 1248 Non-zero exit status: 5 Files=12, Tests=1997, 20 wallclock secs ( 0.50 usr 0.27 sys + 15.59 cusr 2.23 csys = 18.59 CPU) Result: FAIL Failed 1/12 test programs. 5/1997 subtests failed. Build step 'Execute shell' marked build as failure
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-12/843/display/redirect> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 843 originally caused by: Started by upstream project "libvirt-perl-build" build number 844 originally caused by: Started by upstream project "libvirt-build" build number 988 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/jenkins17241670173171632470.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 'virDomainAgentSetResponseTimeout' # at t/030-api-coverage.t line 161. # Failed test 'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_BLOCK' # at t/030-api-coverage.t line 175. # Failed test 'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_DEFAULT' # at t/030-api-coverage.t line 175. # Failed test 'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_NOWAIT' # at t/030-api-coverage.t line 175. # Failed test 'VIR_FROM_BPF' # at t/030-api-coverage.t line 175. # Looks like you failed 5 tests of 1739. t/030-api-coverage.t ... Dubious, test returned 5 (wstat 1280, 0x500) Failed 5/1739 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: 1280 Tests: 1739 Failed: 5) Failed tests: 113, 655-657, 1248 Non-zero exit status: 5 Files=12, Tests=1997, 65 wallclock secs ( 0.94 usr 0.37 sys + 19.84 cusr 1.98 csys = 23.12 CPU) Result: FAIL Failed 1/12 test programs. 5/1997 subtests failed. Build step 'Execute shell' marked build as failure
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-12/844/display/redirect> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 844 originally caused by: Started by upstream project "libvirt-perl-build" build number 845 originally caused by: Started by upstream project "libvirt-build" build number 989 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/jenkins6212982698463819704.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 'virDomainAgentSetResponseTimeout' # at t/030-api-coverage.t line 161. # Failed test 'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_BLOCK' # at t/030-api-coverage.t line 175. # Failed test 'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_DEFAULT' # at t/030-api-coverage.t line 175. # Failed test 'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_NOWAIT' # at t/030-api-coverage.t line 175. # Failed test 'VIR_FROM_BPF' # at t/030-api-coverage.t line 175. # Looks like you failed 5 tests of 1739. t/030-api-coverage.t ... Dubious, test returned 5 (wstat 1280, 0x500) Failed 5/1739 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: 1280 Tests: 1739 Failed: 5) Failed tests: 113, 655-657, 1248 Non-zero exit status: 5 Files=12, Tests=1997, 31 wallclock secs ( 0.76 usr 0.37 sys + 20.06 cusr 3.04 csys = 24.23 CPU) Result: FAIL Failed 1/12 test programs. 5/1997 subtests failed. Build step 'Execute shell' marked build as failure
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-12/845/display/redirect> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 845 originally caused by: Started by upstream project "libvirt-perl-build" build number 846 originally caused by: Started by upstream project "libvirt-build" build number 990 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 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/jenkins11272403152434990840.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 'virDomainAgentSetResponseTimeout' # at t/030-api-coverage.t line 161. # Failed test 'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_BLOCK' # at t/030-api-coverage.t line 175. # Failed test 'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_DEFAULT' # at t/030-api-coverage.t line 175. # Failed test 'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_NOWAIT' # at t/030-api-coverage.t line 175. # Failed test 'VIR_FROM_BPF' # at t/030-api-coverage.t line 175. # Looks like you failed 5 tests of 1739. t/030-api-coverage.t ... Dubious, test returned 5 (wstat 1280, 0x500) Failed 5/1739 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: 1280 Tests: 1739 Failed: 5) Failed tests: 113, 655-657, 1248 Non-zero exit status: 5 Files=12, Tests=1997, 28 wallclock secs ( 0.82 usr 0.30 sys + 19.23 cusr 1.84 csys = 22.20 CPU) Result: FAIL Failed 1/12 test programs. 5/1997 subtests failed. Build step 'Execute shell' marked build as failure
participants (1)
-
ci＠centos.org