- CI - libvirt List Archives

Build failed in Jenkins: libvirt-go-xml-check » libvirt-freebsd-11 #973
by ci＠centos.org 10 Feb '20

10 Feb '20

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-freebsd-11/9…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 973 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 976 originally caused by: Started by upstream project "libvirt-build" build number 1142 originally caused by: Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on libvirt-freebsd-11 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-freebsd-11/w…> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins12465052243419893166.sh + export 'TEST_ARGS=-tags xmlroundtrip' + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (23.61s) xml_test.go:374: testdata/libvirt/tests/qemuxml2argvdata/net-virtio-teaming-network.xml: /domain[0]/devices[0]/interface[0]/teaming[0]: element in expected XML missing in actual XML FAIL exit status 1 FAIL _/usr<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-freebsd-11/w…> 23.719s Build step 'Execute shell' marked build as failure

1 29

Build failed in Jenkins: libvirt-go-xml-check » libvirt-freebsd-12 #973
by ci＠centos.org 10 Feb '20

10 Feb '20

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-freebsd-12/9…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 973 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 976 originally caused by: Started by upstream project "libvirt-build" build number 1142 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-go-xml-check/systems=libvirt-freebsd-12/w…> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins15383368374117587613.sh + export 'TEST_ARGS=-tags xmlroundtrip' + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (15.54s) xml_test.go:374: testdata/libvirt/tests/qemuxml2argvdata/net-virtio-teaming-network.xml: /domain[0]/devices[0]/interface[0]/teaming[0]: element in expected XML missing in actual XML FAIL exit status 1 FAIL _/usr<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-freebsd-12/w…> 15.698s Build step 'Execute shell' marked build as failure

1 29

Build failed in Jenkins: libvirt-go-xml-check » libvirt-fedora-30 #973
by ci＠centos.org 10 Feb '20

10 Feb '20

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-30/97…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 973 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 976 originally caused by: Started by upstream project "libvirt-build" build number 1142 originally caused by: 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-go-xml-check/systems=libvirt-fedora-30/ws/> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins7629761787415494404.sh + export 'TEST_ARGS=-tags xmlroundtrip' + TEST_ARGS='-tags xmlroundtrip' + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (44.15s) xml_test.go:374: testdata/libvirt/tests/qemuxml2argvdata/net-virtio-teaming-network.xml: /domain[0]/devices[0]/interface[0]/teaming[0]: element in expected XML missing in actual XML FAIL exit status 1 FAIL _<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-30/ws/> 44.368s Build step 'Execute shell' marked build as failure

1 29

Build failed in Jenkins: libvirt-go-xml-check » libvirt-fedora-31 #973
by ci＠centos.org 10 Feb '20

10 Feb '20

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-31/97…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 973 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 976 originally caused by: Started by upstream project "libvirt-build" build number 1142 originally caused by: Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-31 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-31/ws/> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins7280514413787676144.sh + export 'TEST_ARGS=-tags xmlroundtrip' + TEST_ARGS='-tags xmlroundtrip' + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (28.58s) xml_test.go:374: testdata/libvirt/tests/qemuxml2argvdata/net-virtio-teaming-network.xml: /domain[0]/devices[0]/interface[0]/teaming[0]: element in expected XML missing in actual XML FAIL exit status 1 FAIL _<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-31/ws/> 28.722s Build step 'Execute shell' marked build as failure

1 29

Build failed in Jenkins: libvirt-go-xml-check » libvirt-centos-7 #973
by ci＠centos.org 10 Feb '20

10 Feb '20

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-centos-7/973…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 973 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 976 originally caused by: Started by upstream project "libvirt-build" build number 1142 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-go-xml-check/systems=libvirt-centos-7/ws/> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins14058072102300925731.sh + export 'TEST_ARGS=-tags xmlroundtrip' + TEST_ARGS='-tags xmlroundtrip' + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (41.73s) xml_test.go:374: testdata/libvirt/tests/qemuxml2argvdata/net-virtio-teaming-network.xml: /domain[0]/devices[0]/interface[0]/teaming[0]: element in expected XML missing in actual XML FAIL exit status 1 FAIL _<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-centos-7/ws/> 41.957s Build step 'Execute shell' marked build as failure

1 29

Build failed in Jenkins: libvirt-go-xml-check » libvirt-debian-10 #973
by ci＠centos.org 10 Feb '20

10 Feb '20

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-debian-10/97…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 973 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 976 originally caused by: Started by upstream project "libvirt-build" build number 1142 originally caused by: Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on libvirt-debian-10 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-debian-10/ws/> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins7524835578563036235.sh + export TEST_ARGS=-tags xmlroundtrip + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (37.37s) xml_test.go:374: testdata/libvirt/tests/qemuxml2argvdata/net-virtio-teaming-network.xml: /domain[0]/devices[0]/interface[0]/teaming[0]: element in expected XML missing in actual XML FAIL exit status 1 FAIL _<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-debian-10/ws/> 37.487s Build step 'Execute shell' marked build as failure

1 29

Build failed in Jenkins: libvirt-go-xml-check » libvirt-debian-9 #973
by ci＠centos.org 10 Feb '20

10 Feb '20

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-debian-9/973…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 973 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 976 originally caused by: Started by upstream project "libvirt-build" build number 1142 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-go-xml-check/systems=libvirt-debian-9/ws/> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins4373460319430543918.sh + export TEST_ARGS=-tags xmlroundtrip + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (36.70s) xml_test.go:374: testdata/libvirt/tests/qemuxml2argvdata/net-virtio-teaming-network.xml: /domain[0]/devices[0]/interface[0]/teaming[0]: element in expected XML missing in actual XML FAIL exit status 1 FAIL _<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-debian-9/ws/> 36.847s Build step 'Execute shell' marked build as failure

1 29

Build failed in Jenkins: libvirt-perl-check » libvirt-freebsd-11 #998
by ci＠centos.org 10 Feb '20

10 Feb '20

See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-11/998…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 998 originally caused by: Started by upstream project "libvirt-perl-build" build number 1000 originally caused by: Started by upstream project "libvirt-build" build number 1168 originally caused by: Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on libvirt-freebsd-11 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-11/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins9972092734623346822.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 'VIR_DOMAIN_EVENT_CRASHED_CRASHLOADED' # at t/030-api-coverage.t line 175. # Looks like you failed 1 test of 1754. t/030-api-coverage.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1754 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: 1754 Failed: 1) Failed test: 750 Non-zero exit status: 1 Files=12, Tests=2012, 46 wallclock secs ( 0.88 usr 0.54 sys + 19.89 cusr 1.78 csys = 23.09 CPU) Result: FAIL Failed 1/12 test programs. 1/2012 subtests failed. Build step 'Execute shell' marked build as failure

1 3

Build failed in Jenkins: libvirt-perl-check » libvirt-fedora-30 #998
by ci＠centos.org 10 Feb '20

10 Feb '20

See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-30/998/…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 998 originally caused by: Started by upstream project "libvirt-perl-build" build number 1000 originally caused by: Started by upstream project "libvirt-build" build number 1168 originally caused by: 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/jenkins4057768491292937599.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_EVENT_CRASHED_CRASHLOADED' # at t/030-api-coverage.t line 175. # Looks like you failed 1 test of 1754. t/030-api-coverage.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1754 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: 1754 Failed: 1) Failed test: 750 Non-zero exit status: 1 Files=12, Tests=2012, 41 wallclock secs ( 0.42 usr 0.07 sys + 8.98 cusr 0.69 csys = 10.16 CPU) Result: FAIL Failed 1/12 test programs. 1/2012 subtests failed. Build step 'Execute shell' marked build as failure

1 3

Build failed in Jenkins: libvirt-perl-check » libvirt-freebsd-12 #998
by ci＠centos.org 10 Feb '20

10 Feb '20

See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-12/998…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 998 originally caused by: Started by upstream project "libvirt-perl-build" build number 1000 originally caused by: Started by upstream project "libvirt-build" build number 1168 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/jenkins15968333646139382948.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 'VIR_DOMAIN_EVENT_CRASHED_CRASHLOADED' # at t/030-api-coverage.t line 175. # Looks like you failed 1 test of 1754. t/030-api-coverage.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1754 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: 1754 Failed: 1) Failed test: 750 Non-zero exit status: 1 Files=12, Tests=2012, 50 wallclock secs ( 0.91 usr 0.70 sys + 18.90 cusr 1.97 csys = 22.47 CPU) Result: FAIL Failed 1/12 test programs. 1/2012 subtests failed. Build step 'Execute shell' marked build as failure

1 3