See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-debian-9/124... ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 1247 originally caused by: Started by upstream project "libvirt-perl-build" build number 1250 originally caused by: Started by upstream project "libvirt-build" build number 1448 originally caused by: 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/jenkins7743381388686374507.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 t/030-api-coverage.t ... ok I/O warning : failed to load external entity "/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cooperlake.xml" libvirt error code: 27, message: XML error: failed to parse xml document '/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cooperlake.xml' # Looks like you planned 25 tests but ran 24. # Looks like your test exited with 2 just after 24. t/100-connect.t ........ Dubious, test returned 2 (wstat 512, 0x200) Failed 1/25 subtests (less 1 skipped subtest: 23 okay) 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/100-connect.t (Wstat: 512 Tests: 24 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 25 tests but ran 24. Files=12, Tests=2012, 52 wallclock secs ( 0.72 usr 0.08 sys + 14.35 cusr 0.68 csys = 15.83 CPU) Result: FAIL Failed 1/12 test programs. 0/2012 subtests failed. Build step 'Execute shell' marked build as failure