March 2019 - CI - libvirt List Archives

[Libvirt-ci] Build failed in Jenkins: libvirt-go-check » libvirt-debian-8 #317
by ci＠centos.org 22 Mar '19

22 Mar '19

See <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-8/317/dis…> ------------------------------------------ Started by upstream project "libvirt-go-check" build number 317 originally caused by: Started by upstream project "libvirt-go-build" build number 323 originally caused by: Started by upstream project "libvirt-build" build number 412 originally caused by: 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-check/systems=libvirt-debian-8/ws/> [libvirt-go] $ /bin/sh -xe /tmp/jenkins5484071794790138633.sh + export TEST_ARGS=-tags api + go test -tags api fatal error: unexpected signal during runtime execution [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x7f906fde8459] runtime stack: runtime.throw(0x5fad14, 0x2a) /usr/lib/go-1.7/src/runtime/panic.go:566 +0x95 runtime.sigpanic() /usr/lib/go-1.7/src/runtime/sigpanic_unix.go:12 +0x2cc goroutine 69 [syscall, locked to thread]: runtime.cgocall(0x58d2a0, 0xc420027e78, 0xc400000000) /usr/lib/go-1.7/src/runtime/cgocall.go:131 +0x110 fp=0xc420027e30 sp=0xc420027df0 _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-8/ws/._Cf…,> 0x7f90600723b0, 0xc400000000, 0xc42045d770, 0x0) ??:0 +0x4e fp=0xc420027e78 sp=0xc420027e30 _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-8/ws/.(*D…,> 0x5fcd6a, 0x7c, 0x0, 0x0, 0x0, 0x0) <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-8/ws/doma…>:4417 +0x220 fp=0xc420027f28 sp=0xc420027e78 _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-8/ws/.Tes…> <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-8/ws/doma…>:236 +0x94 fp=0xc420027f88 sp=0xc420027f28 testing.tRunner(0xc420079140, 0x609020) /usr/lib/go-1.7/src/testing/testing.go:610 +0x81 fp=0xc420027fb0 sp=0xc420027f88 runtime.goexit() /usr/lib/go-1.7/src/runtime/asm_amd64.s:2086 +0x1 fp=0xc420027fb8 sp=0xc420027fb0 created by testing.(*T).Run /usr/lib/go-1.7/src/testing/testing.go:646 +0x2ec goroutine 1 [chan receive]: testing.(*T).Run(0xc4200780c0, 0x5f688f, 0x1b, 0x609020, 0xc42004bd01) /usr/lib/go-1.7/src/testing/testing.go:647 +0x316 testing.RunTests.func1(0xc4200780c0) /usr/lib/go-1.7/src/testing/testing.go:793 +0x6d testing.tRunner(0xc4200780c0, 0xc42003be30) /usr/lib/go-1.7/src/testing/testing.go:610 +0x81 testing.RunTests(0x609948, 0x8ca700, 0x76, 0x76, 0x41d2aa) /usr/lib/go-1.7/src/testing/testing.go:799 +0x2f5 testing.(*M).Run(0xc42003bef8, 0x4ce7cb) /usr/lib/go-1.7/src/testing/testing.go:743 +0x85 main.main() _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-8/ws/_tes…>:288 +0xc6 goroutine 17 [syscall, locked to thread]: runtime.goexit() /usr/lib/go-1.7/src/runtime/asm_amd64.s:2086 +0x1 exit status 2 FAIL _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-8/ws/> 1.177s Build step 'Execute shell' marked build as failure

1 1

[Libvirt-ci] Build failed in Jenkins: libvirt-go-check » libvirt-fedora-29 #317
by ci＠centos.org 22 Mar '19

22 Mar '19

See <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-fedora-29/317/di…> ------------------------------------------ Started by upstream project "libvirt-go-check" build number 317 originally caused by: Started by upstream project "libvirt-go-build" build number 323 originally caused by: Started by upstream project "libvirt-build" build number 412 originally caused by: 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-check/systems=libvirt-fedora-29/ws/> [libvirt-go] $ /bin/sh -xe /tmp/jenkins6691699904511862479.sh + export 'TEST_ARGS=-tags api' + TEST_ARGS='-tags api' + go test -tags api fatal error: unexpected signal during runtime execution [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x7f055d368cf5] runtime stack: runtime.throw(0x618805, 0x2a) /usr/lib/golang/src/runtime/panic.go:608 +0x72 runtime.sigpanic() /usr/lib/golang/src/runtime/signal_unix.go:374 +0x2f2 goroutine 71 [syscall]: runtime.cgocall(0x5a1640, 0xc00010ce90, 0x29) /usr/lib/golang/src/runtime/cgocall.go:128 +0x5e fp=0xc00010ce58 sp=0xc00010ce20 pc=0x41ed5e _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-fedora-29/ws/._C…,> 0x242ed00, 0xc000000000, 0xc000102d70, 0x0) _cgo_gotypes.go:5631 +0x4e fp=0xc00010ce90 sp=0xc00010ce58 pc=0x56579e _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-fedora-29/ws/.(*…,> 0x242ed00, 0x0, 0xc000102d70, 0xc00000e188) <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-fedora-29/ws/dom…>:4417 +0xe4 fp=0xc00010cec8 sp=0xc00010ce90 pc=0x590554 _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-fedora-29/ws/.(*…,> 0x61ac7d, 0x7c, 0x0, 0x0, 0x0, 0x0) <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-fedora-29/ws/dom…>:4417 +0xc9 fp=0xc00010cf48 sp=0xc00010cec8 pc=0x5762d9 _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-fedora-29/ws/.Te…> <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-fedora-29/ws/dom…>:232 +0x94 fp=0xc00010cfa8 sp=0xc00010cf48 pc=0x557c84 testing.tRunner(0xc000439f00, 0x61b180) /usr/lib/golang/src/testing/testing.go:827 +0xbf fp=0xc00010cfd0 sp=0xc00010cfa8 pc=0x4e858f runtime.goexit() /usr/lib/golang/src/runtime/asm_amd64.s:1333 +0x1 fp=0xc00010cfd8 sp=0xc00010cfd0 pc=0x475b11 created by testing.(*T).Run /usr/lib/golang/src/testing/testing.go:878 +0x35c goroutine 1 [chan receive]: testing.(*T).Run(0xc000439f00, 0x613e01, 0x1b, 0x61b180, 0x48f801) /usr/lib/golang/src/testing/testing.go:879 +0x383 testing.runTests.func1(0xc0000c2000) /usr/lib/golang/src/testing/testing.go:1119 +0x78 testing.tRunner(0xc0000c2000, 0xc0000a1e08) /usr/lib/golang/src/testing/testing.go:827 +0xbf testing.runTests(0xc0000900c0, 0x777aa0, 0x76, 0x76, 0x42788f) /usr/lib/golang/src/testing/testing.go:1117 +0x2aa testing.(*M).Run(0xc0000c0000, 0x0) /usr/lib/golang/src/testing/testing.go:1034 +0x165 main.main() _testmain.go:276 +0x13d exit status 2 FAIL _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-fedora-29/ws/> 2.038s Build step 'Execute shell' marked build as failure

1 1

[Libvirt-ci] Build failed in Jenkins: libvirt-go-check » libvirt-freebsd-12 #317
by ci＠centos.org 22 Mar '19

22 Mar '19

See <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-freebsd-12/317/d…> ------------------------------------------ Started by upstream project "libvirt-go-check" build number 317 originally caused by: Started by upstream project "libvirt-go-build" build number 323 originally caused by: Started by upstream project "libvirt-build" build number 412 originally caused by: 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-go-check/systems=libvirt-freebsd-12/ws/> [libvirt-go] $ /bin/sh -xe /tmp/jenkins5951381697665088410.sh + export 'TEST_ARGS=-tags api' + go test -tags api fatal error: unexpected signal during runtime execution [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x8007ffa53] runtime stack: runtime.throw(0x270784, 0x2a) /usr/local/go/src/runtime/panic.go:617 +0x72 runtime.sigpanic() /usr/local/go/src/runtime/signal_unix.go:374 +0x4a9 goroutine 69 [syscall]: runtime.cgocall(0x582680, 0xc000440e88, 0xc0000e51d0) /usr/local/go/src/runtime/cgocall.go:128 +0x5b fp=0xc000440e58 sp=0xc000440e20 pc=0x3fe21b _/usr<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-freebsd-12/ws/._…,> 0x805613800, 0xc000000000, 0xc0000e51d0, 0x0) _cgo_gotypes.go:5641 +0x4e fp=0xc000440e88 sp=0xc000440e58 pc=0x54493e _/usr<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-freebsd-12/ws/.(…,> 0x805613800, 0x0, 0xc0000e51d0, 0xc0000101d0) /usr<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-freebsd-12/ws/do…>:4417 +0xed fp=0xc000440ec8 sp=0xc000440e88 pc=0x56ff0d _/usr<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-freebsd-12/ws/.(…,> 0x272ba5, 0x7c, 0x0, 0x0, 0x0, 0x0) /usr<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-freebsd-12/ws/do…>:4417 +0xc4 fp=0xc000440f48 sp=0xc000440ec8 pc=0x554f74 _/usr<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-freebsd-12/ws/.T…> /usr<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-freebsd-12/ws/do…>:232 +0x94 fp=0xc000440fa8 sp=0xc000440f48 pc=0x537c44 testing.tRunner(0xc000389f00, 0x272fb0) /usr/local/go/src/testing/testing.go:865 +0xc0 fp=0xc000440fd0 sp=0xc000440fa8 pc=0x4c7bf0 runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1337 +0x1 fp=0xc000440fd8 sp=0xc000440fd0 pc=0x4548c1 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:916 +0x35a goroutine 1 [chan receive]: testing.(*T).Run(0xc000389f00, 0x26bd20, 0x1b, 0x272fb0, 0x46e301) /usr/local/go/src/testing/testing.go:917 +0x381 testing.runTests.func1(0xc0000c8000) /usr/local/go/src/testing/testing.go:1157 +0x78 testing.tRunner(0xc0000c8000, 0xc0000a7e30) /usr/local/go/src/testing/testing.go:865 +0xc0 testing.runTests(0xc0000940c0, 0x5935c0, 0x76, 0x76, 0x0) /usr/local/go/src/testing/testing.go:1155 +0x2a9 testing.(*M).Run(0xc0000c6000, 0x0) /usr/local/go/src/testing/testing.go:1072 +0x162 main.main() _testmain.go:276 +0x13e exit status 2 FAIL _/usr<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-freebsd-12/ws/> 1.598s Build step 'Execute shell' marked build as failure

1 1

[Libvirt-ci] Build failed in Jenkins: libvirt-go-check » libvirt-freebsd-11 #317
by ci＠centos.org 22 Mar '19

22 Mar '19

See <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-freebsd-11/317/d…> ------------------------------------------ Started by upstream project "libvirt-go-check" build number 317 originally caused by: Started by upstream project "libvirt-go-build" build number 323 originally caused by: Started by upstream project "libvirt-build" build number 412 originally caused by: 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-check/systems=libvirt-freebsd-11/ws/> [libvirt-go] $ /bin/sh -xe /tmp/jenkins7652619563135812477.sh + export 'TEST_ARGS=-tags api' + go test -tags api fatal error: unexpected signal during runtime execution [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x80115d803] runtime stack: runtime.throw(0x61dd24, 0x2a) /usr/local/go/src/runtime/panic.go:617 +0x72 runtime.sigpanic() /usr/local/go/src/runtime/signal_unix.go:374 +0x4a9 goroutine 62 [syscall]: runtime.cgocall(0x5a6020, 0xc000046e88, 0xc0000c4140) /usr/local/go/src/runtime/cgocall.go:128 +0x5b fp=0xc000046e58 sp=0xc000046e20 pc=0x421bbb _/usr<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-freebsd-11/ws/._…,> 0x80aeeae80, 0xc000000000, 0xc0000c4140, 0x0) _cgo_gotypes.go:5641 +0x4e fp=0xc000046e88 sp=0xc000046e58 pc=0x5682de _/usr<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-freebsd-11/ws/.(…,> 0x80aeeae80, 0x0, 0xc0000c4140, 0xc0000de150) /usr<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-freebsd-11/ws/do…>:4417 +0xed fp=0xc000046ec8 sp=0xc000046e88 pc=0x5938ad _/usr<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-freebsd-11/ws/.(…,> 0x620145, 0x7c, 0x0, 0x0, 0x0, 0x0) /usr<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-freebsd-11/ws/do…>:4417 +0xc4 fp=0xc000046f48 sp=0xc000046ec8 pc=0x578914 _/usr<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-freebsd-11/ws/.T…> /usr<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-freebsd-11/ws/do…>:232 +0x94 fp=0xc000046fa8 sp=0xc000046f48 pc=0x55b5e4 testing.tRunner(0xc0000b9500, 0x620550) /usr/local/go/src/testing/testing.go:865 +0xc0 fp=0xc000046fd0 sp=0xc000046fa8 pc=0x4eb590 runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1337 +0x1 fp=0xc000046fd8 sp=0xc000046fd0 pc=0x478261 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:916 +0x35a goroutine 1 [chan receive]: testing.(*T).Run(0xc0000b9500, 0x6192c0, 0x1b, 0x620550, 0x491c01) /usr/local/go/src/testing/testing.go:917 +0x381 testing.runTests.func1(0xc0000b8000) /usr/local/go/src/testing/testing.go:1157 +0x78 testing.tRunner(0xc0000b8000, 0xc00008de30) /usr/local/go/src/testing/testing.go:865 +0xc0 testing.runTests(0xc0000b4000, 0x990900, 0x76, 0x76, 0x0) /usr/local/go/src/testing/testing.go:1155 +0x2a9 testing.(*M).Run(0xc0000ac000, 0x0) /usr/local/go/src/testing/testing.go:1072 +0x162 main.main() _testmain.go:276 +0x13e goroutine 72 [runnable]: runtime.goexit1() /usr/local/go/src/runtime/proc.go:2652 +0x6b runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1338 +0x6 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:916 +0x35a exit status 2 FAIL _/usr<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-freebsd-11/ws/> 1.330s Build step 'Execute shell' marked build as failure

1 1

[Libvirt-ci] Build failed in Jenkins: virt-manager-check » libvirt-fedora-28 #542
by ci＠centos.org 22 Mar '19

22 Mar '19

See <https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-28/542/…> ------------------------------------------ Started by upstream project "virt-manager-check" build number 542 originally caused by: Started by upstream project "virt-manager-build" build number 545 originally caused by: Started by upstream project "libvirt-python-build" build number 326 originally caused by: Started by upstream project "libvirt-build" build number 412 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-28 (libvirt) in workspace <https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-28/ws/> [virt-manager] $ /bin/sh -xe /tmp/jenkins2679033847838418988.sh + /usr/bin/python3 ./setup.py test running test .../tmp/jenkins2679033847838418988.sh: line 3: 1753 Segmentation fault (core dumped) $PYTHON ./setup.py test Build step 'Execute shell' marked build as failure

1 1

[Libvirt-ci] Build failed in Jenkins: virt-manager-check » libvirt-fedora-29 #542
by ci＠centos.org 22 Mar '19

22 Mar '19

See <https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-29/542/…> ------------------------------------------ Started by upstream project "virt-manager-check" build number 542 originally caused by: Started by upstream project "virt-manager-build" build number 545 originally caused by: Started by upstream project "libvirt-python-build" build number 326 originally caused by: Started by upstream project "libvirt-build" build number 412 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-29 (libvirt) in workspace <https://ci.centos.org/job/virt-manager-check/systems=libvirt-fedora-29/ws/> [virt-manager] $ /bin/sh -xe /tmp/jenkins8571457106041359326.sh + /usr/bin/python3 ./setup.py test running test .../tmp/jenkins8571457106041359326.sh: line 3: 10398 Segmentation fault (core dumped) $PYTHON ./setup.py test Build step 'Execute shell' marked build as failure

1 1

[Libvirt-ci] Build failed in Jenkins: virt-manager-check » libvirt-debian-9 #542
by ci＠centos.org 22 Mar '19

22 Mar '19

See <https://ci.centos.org/job/virt-manager-check/systems=libvirt-debian-9/542/d…> ------------------------------------------ Started by upstream project "virt-manager-check" build number 542 originally caused by: Started by upstream project "virt-manager-build" build number 545 originally caused by: Started by upstream project "libvirt-python-build" build number 326 originally caused by: Started by upstream project "libvirt-build" build number 412 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-debian-9 (libvirt) in workspace <https://ci.centos.org/job/virt-manager-check/systems=libvirt-debian-9/ws/> [virt-manager] $ /bin/sh -xe /tmp/jenkins8239744184952119892.sh + /usr/bin/python3 ./setup.py test running test ...Segmentation fault Build step 'Execute shell' marked build as failure

1 1

[Libvirt-ci] Build failed in Jenkins: libvirt-go-xml-check » libvirt-fedora-rawhide #318
by ci＠centos.org 20 Mar '19

20 Mar '19

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-rawhi…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 318 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 318 originally caused by: Started by upstream project "libvirt-build" build number 402 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-rawhide (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-rawhi…> [libvirt-go-xml] $ /bin/sh -xe /tmp/jenkins6970841105679994335.sh + export 'TEST_ARGS=-tags xmlroundtrip' + TEST_ARGS='-tags xmlroundtrip' + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (16.16s) xml_test.go:394: testdata/libvirt/tests/domaincapsschemadata/empty.xml: /domainCapabilities[0]/os[0]: element in actual XML missing in expected XML FAIL exit status 1 FAIL _<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-fedora-rawhi…> 16.389s Build step 'Execute shell' marked build as failure

1 4

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

20 Mar '19

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-debian-9/318…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 318 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 318 originally caused by: Started by upstream project "libvirt-build" build number 402 originally caused by: 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/jenkins1238327957738189325.sh + export TEST_ARGS=-tags xmlroundtrip + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (8.66s) xml_test.go:394: testdata/libvirt/tests/domaincapsschemadata/empty.xml: /domainCapabilities[0]/os[0]: element in actual XML missing in expected XML FAIL exit status 1 FAIL _<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-debian-9/ws/> 8.697s Build step 'Execute shell' marked build as failure

1 4

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

20 Mar '19

See <https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-debian-8/318…> ------------------------------------------ Started by upstream project "libvirt-go-xml-check" build number 318 originally caused by: Started by upstream project "libvirt-go-xml-build" build number 318 originally caused by: Started by upstream project "libvirt-build" build number 402 originally caused by: 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/jenkins861870069089213012.sh + export TEST_ARGS=-tags xmlroundtrip + go test -tags xmlroundtrip --- FAIL: TestRoundTrip (9.03s) xml_test.go:394: testdata/libvirt/tests/domaincapsschemadata/empty.xml: /domainCapabilities[0]/os[0]: element in actual XML missing in expected XML FAIL exit status 1 FAIL _<https://ci.centos.org/job/libvirt-go-xml-check/systems=libvirt-debian-8/ws/> 9.074s Build step 'Execute shell' marked build as failure

1 4