[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-fedora-30 #545

ci at centos.org ci at centos.org
Mon Jul 15 13:12:42 UTC 2019 

See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-30/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-30 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-30/ws/>
[libvirt-perl] $ /bin/sh -xe /tmp/jenkins3859600367191696540.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.42 usr  0.05 sys +  9.14 cusr  0.64 csys = 10.25 CPU)
Result: FAIL
Failed 1/12 test programs. 1/1944 subtests failed.
Build step 'Execute shell' marked build as failure

More information about the Libvirt-ci mailing list