12:43 p.m.
See
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-centos-7/840...
------------------------------------------
[...truncated 20.68 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
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/jenkins8675388590448962684.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 '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.41 usr 0.05 sys + 8.46 cusr 0.38 csys =
9.30 CPU)
Result: FAIL
Failed 1/12 test programs. 5/1997 subtests failed.
Build step 'Execute shell' marked build as failure
5:21 a.m.
New subject: [Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-centos-7 #841
See
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-centos-7/841...
------------------------------------------
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-centos-7 (libvirt) in workspace
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-centos-7/ws/...
[libvirt-perl] $ /bin/sh -xe /tmp/jenkins12595377638457494086.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 '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, 43 wallclock secs ( 0.44 usr 0.06 sys + 9.23 cusr 0.43 csys =
10.16 CPU)
Result: FAIL
Failed 1/12 test programs. 5/1997 subtests failed.
Build step 'Execute shell' marked build as failure
8:20 a.m.
New subject: [Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-centos-7 #842
See
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-centos-7/842...
------------------------------------------
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-centos-7 (libvirt) in workspace
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-centos-7/ws/...
[libvirt-perl] $ /bin/sh -xe /tmp/jenkins4471184987123172093.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 '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, 36 wallclock secs ( 0.41 usr 0.05 sys + 8.55 cusr 0.42 csys =
9.43 CPU)
Result: FAIL
Failed 1/12 test programs. 5/1997 subtests failed.
Build step 'Execute shell' marked build as failure
9:43 a.m.
New subject: [Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-centos-7 #843
See
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-centos-7/843...
------------------------------------------
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-centos-7 (libvirt) in workspace
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-centos-7/ws/...
[libvirt-perl] $ /bin/sh -xe /tmp/jenkins5254121416994048567.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 '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, 46 wallclock secs ( 0.42 usr 0.05 sys + 8.52 cusr 0.38 csys =
9.37 CPU)
Result: FAIL
Failed 1/12 test programs. 5/1997 subtests failed.
Build step 'Execute shell' marked build as failure
9:11 a.m.
New subject: [Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-centos-7 #844
See
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-centos-7/844...
------------------------------------------
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-centos-7 (libvirt) in workspace
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-centos-7/ws/...
[libvirt-perl] $ /bin/sh -xe /tmp/jenkins9694540111029559595.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 '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.38 usr 0.06 sys + 8.35 cusr 0.56 csys =
9.35 CPU)
Result: FAIL
Failed 1/12 test programs. 5/1997 subtests failed.
Build step 'Execute shell' marked build as failure
10:47 a.m.
New subject: [Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-centos-7 #845
See
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-centos-7/845...
------------------------------------------
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-centos-7 (libvirt) in workspace
<https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-centos-7/ws/...
[libvirt-perl] $ /bin/sh -xe /tmp/jenkins11623690108771082815.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 '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, 25 wallclock secs ( 0.42 usr 0.04 sys + 8.44 cusr 0.40 csys =
9.30 CPU)
Result: FAIL
Failed 1/12 test programs. 5/1997 subtests failed.
Build step 'Execute shell' marked build as failure
8:59 a.m.
New subject: [Libvirt-ci] Jenkins build is back to normal : libvirt-perl-check » libvirt-centos-7 #846
1812
days inactive
1817
days old
6 comments
1 participants
participants (1)
-
ci＠centos.org