February 2019 - CI - libvirt List Archives

[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-debian-9 #222
by ci＠centos.org 04 Feb '19

04 Feb '19

See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-debian-9/222/d…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 222 originally caused by: Started by upstream project "libvirt-perl-build" build number 222 originally caused by: Started by upstream project "libvirt-build" build number 281 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 [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/jenkins730403103761789286.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_FROM_FIREWALLD' # at t/030-api-coverage.t line 175. # Looks like you failed 1 test of 1648. t/030-api-coverage.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1648 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: 1648 Failed: 1) Failed test: 1194 Non-zero exit status: 1 Files=12, Tests=1902, 25 wallclock secs ( 0.51 usr 0.08 sys + 9.18 cusr 0.43 csys = 10.20 CPU) Result: FAIL Failed 1/12 test programs. 1/1902 subtests failed. Build step 'Execute shell' marked build as failure

1 3

[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-centos-7 #222
by ci＠centos.org 04 Feb '19

04 Feb '19

See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-centos-7/222/d…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 222 originally caused by: Started by upstream project "libvirt-perl-build" build number 222 originally caused by: Started by upstream project "libvirt-build" build number 281 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 [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/jenkins1590745935353620772.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_FROM_FIREWALLD' # at t/030-api-coverage.t line 175. # Looks like you failed 1 test of 1648. t/030-api-coverage.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1648 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: 1648 Failed: 1) Failed test: 1194 Non-zero exit status: 1 Files=12, Tests=1902, 30 wallclock secs ( 0.45 usr 0.04 sys + 8.29 cusr 0.41 csys = 9.19 CPU) Result: FAIL Failed 1/12 test programs. 1/1902 subtests failed. Build step 'Execute shell' marked build as failure

1 3

[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-freebsd-11 #222
by ci＠centos.org 04 Feb '19

04 Feb '19

See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-11/222…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 222 originally caused by: Started by upstream project "libvirt-perl-build" build number 222 originally caused by: Started by upstream project "libvirt-build" build number 281 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 [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/jenkins348502123604485069.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_FROM_FIREWALLD' # at t/030-api-coverage.t line 175. # Looks like you failed 1 test of 1648. t/030-api-coverage.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1648 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: 1648 Failed: 1) Failed test: 1194 Non-zero exit status: 1 Files=12, Tests=1902, 17 wallclock secs ( 0.47 usr 0.27 sys + 14.17 cusr 1.50 csys = 16.41 CPU) Result: FAIL Failed 1/12 test programs. 1/1902 subtests failed. Build step 'Execute shell' marked build as failure

1 3

[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-freebsd-12 #222
by ci＠centos.org 04 Feb '19

04 Feb '19

See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-12/222…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 222 originally caused by: Started by upstream project "libvirt-perl-build" build number 222 originally caused by: Started by upstream project "libvirt-build" build number 281 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 [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/jenkins8096675720691003207.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_FROM_FIREWALLD' # at t/030-api-coverage.t line 175. # Looks like you failed 1 test of 1648. t/030-api-coverage.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1648 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: 1648 Failed: 1) Failed test: 1194 Non-zero exit status: 1 Files=12, Tests=1902, 17 wallclock secs ( 0.38 usr 0.38 sys + 13.51 cusr 2.20 csys = 16.46 CPU) Result: FAIL Failed 1/12 test programs. 1/1902 subtests failed. Build step 'Execute shell' marked build as failure

1 3

[Libvirt-ci] Build failed in Jenkins: libvirt-go-xml-check » libvirt-fedora-29 #222
by ci＠centos.org 04 Feb '19

04 Feb '19

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-29/22…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 222 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 222 originally caused by: Started by upstream project "libvirt-build" build number 280 originally caused by: Started by an SCM change Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-29 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-29/ws/> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins6081532051443757315.sh + export 'TEST_ARGS=-tags xmlroundtrip' + TEST_ARGS='-tags xmlroundtrip' + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (6.69s) xml_test.go:400: testdata/libvirt/tests/networkxml2xmlin/routed-network.xml: /network[0]/bridge[0]/@zone: attribute 'myzone' in expected XML missing in actual XML FAIL exit status 1 FAIL _<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-29/ws/> 6.801s Build step 'Execute shell' marked build as failure

1 4

[Libvirt-ci] Build failed in Jenkins: libvirt-go-xml-check » libvirt-fedora-28 #222
by ci＠centos.org 04 Feb '19

04 Feb '19

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-28/22…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 222 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 222 originally caused by: Started by upstream project "libvirt-build" build number 280 originally caused by: Started by an SCM change Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-28 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-28/ws/> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins517873475565953016.sh + export 'TEST_ARGS=-tags xmlroundtrip' + TEST_ARGS='-tags xmlroundtrip' + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (14.14s) xml_test.go:400: testdata/libvirt/tests/networkxml2xmlin/routed-network.xml: /network[0]/bridge[0]/@zone: attribute 'myzone' in expected XML missing in actual XML FAIL exit status 1 FAIL _<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-28/ws/> 14.308s Build step 'Execute shell' marked build as failure

1 4

[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-debian-8 #222
by ci＠centos.org 04 Feb '19

04 Feb '19

See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-debian-8/222/d…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 222 originally caused by: Started by upstream project "libvirt-perl-build" build number 222 originally caused by: Started by upstream project "libvirt-build" build number 281 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 [EnvInject] - Loading node environment variables. Building remotely on libvirt-debian-8 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-debian-8/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins9096836799252655713.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_FROM_FIREWALLD' # at t/030-api-coverage.t line 175. # Looks like you failed 1 test of 1648. t/030-api-coverage.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1648 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: 1648 Failed: 1) Failed test: 1194 Non-zero exit status: 1 Files=12, Tests=1902, 19 wallclock secs ( 0.61 usr 0.07 sys + 11.35 cusr 0.60 csys = 12.63 CPU) Result: FAIL Failed 1/12 test programs. 1/1902 subtests failed. Build step 'Execute shell' marked build as failure

1 3

[Libvirt-ci] Build failed in Jenkins: libvirt-go-xml-check » libvirt-debian-9 #222
by ci＠centos.org 04 Feb '19

04 Feb '19

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-debian-9/222…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 222 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 222 originally caused by: Started by upstream project "libvirt-build" build number 280 originally caused by: Started by an SCM change Started by an SCM change Started by an SCM change [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/jenkins1405547355613435202.sh + export TEST_ARGS=-tags xmlroundtrip + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (12.97s) xml_test.go:400: testdata/libvirt/tests/networkxml2xmlin/routed-network.xml: /network[0]/bridge[0]/@zone: attribute 'myzone' 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/> 13.032s Build step 'Execute shell' marked build as failure

1 4

[Libvirt-ci] Build failed in Jenkins: libvirt-go-xml-check » libvirt-debian-8 #222
by ci＠centos.org 04 Feb '19

04 Feb '19

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-debian-8/222…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 222 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 222 originally caused by: Started by upstream project "libvirt-build" build number 280 originally caused by: Started by an SCM change Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-debian-8 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-debian-8/ws/> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins804672907747200270.sh + export TEST_ARGS=-tags xmlroundtrip + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (22.42s) xml_test.go:400: testdata/libvirt/tests/networkxml2xmlin/routed-network.xml: /network[0]/bridge[0]/@zone: attribute 'myzone' in expected XML missing in actual XML FAIL exit status 1 FAIL _<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-debian-8/ws/> 22.599s Build step 'Execute shell' marked build as failure

1 4

[Libvirt-ci] Build failed in Jenkins: libvirt-go-xml-check » libvirt-freebsd-11 #222
by ci＠centos.org 04 Feb '19

04 Feb '19

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-freebsd-11/2…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 222 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 222 originally caused by: Started by upstream project "libvirt-build" build number 280 originally caused by: Started by an SCM change Started by an SCM change Started by an SCM change [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/jenkins8472822644540285294.sh + export 'TEST_ARGS=-tags xmlroundtrip' + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (8.15s) xml_test.go:400: testdata/libvirt/tests/networkxml2xmlin/routed-network.xml: /network[0]/bridge[0]/@zone: attribute 'myzone' 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…> 8.273s Build step 'Execute shell' marked build as failure

1 4