[Libvirt-ci] Build failed in Jenkins: libvirt-go-check » libvirt-debian-9 #531
See <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/531/display/redirect> ------------------------------------------ Started by upstream project "libvirt-go-check" build number 531 originally caused by: Started by upstream project "libvirt-go-build" build number 539 originally caused by: Started by upstream project "libvirt-build" build number 651 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-check/systems=libvirt-debian-9/ws/> [libvirt-go] $ /bin/sh -xe /tmp/jenkins2374613575100168535.sh + export TEST_ARGS=-tags api + go test -tags api Missing enum 'VIR_DOMAIN_SNAPSHOT_CREATE_VALIDATE' --- FAIL: TestAPICoverage (0.17s) panic: Missing symbols found [recovered] panic: Missing symbols found goroutine 19 [running]: panic(0x562e81bf8300, 0xc42042cd20) /usr/lib/go-1.7/src/runtime/panic.go:500 +0x1a1 testing.tRunner.func1(0xc420086180) /usr/lib/go-1.7/src/testing/testing.go:579 +0x25d panic(0x562e81bf8300, 0xc42042cd20) /usr/lib/go-1.7/src/runtime/panic.go:458 +0x243 _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/.TestAPICoverage(0xc420086180)> <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/api_test.go>:501 +0x5ff testing.tRunner(0xc420086180, 0x562e81c4ba88) /usr/lib/go-1.7/src/testing/testing.go:610 +0x81 created by testing.(*T).Run /usr/lib/go-1.7/src/testing/testing.go:646 +0x2ec exit status 2 FAIL _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/> 0.214s Build step 'Execute shell' marked build as failure
See <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/532/display/redirect> ------------------------------------------ Started by upstream project "libvirt-go-check" build number 532 originally caused by: Started by upstream project "libvirt-go-build" build number 540 originally caused by: Started by upstream project "libvirt-build" build number 652 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 [EnvInject] - Loading node environment variables. Building remotely on libvirt-debian-9 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/> [libvirt-go] $ /bin/sh -xe /tmp/jenkins5387605416936079913.sh + export TEST_ARGS=-tags api + go test -tags api Missing enum 'VIR_DOMAIN_SNAPSHOT_CREATE_VALIDATE' --- FAIL: TestAPICoverage (1.22s) panic: Missing symbols found [recovered] panic: Missing symbols found goroutine 5 [running]: panic(0x56157acd1300, 0xc420430df0) /usr/lib/go-1.7/src/runtime/panic.go:500 +0x1a1 testing.tRunner.func1(0xc420078180) /usr/lib/go-1.7/src/testing/testing.go:579 +0x25d panic(0x56157acd1300, 0xc420430df0) /usr/lib/go-1.7/src/runtime/panic.go:458 +0x243 _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/.TestAPICoverage(0xc420078180)> <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/api_test.go>:501 +0x5ff testing.tRunner(0xc420078180, 0x56157ad24a88) /usr/lib/go-1.7/src/testing/testing.go:610 +0x81 created by testing.(*T).Run /usr/lib/go-1.7/src/testing/testing.go:646 +0x2ec exit status 2 FAIL _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/> 1.380s Build step 'Execute shell' marked build as failure
See <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/533/display/redirect> ------------------------------------------ Started by upstream project "libvirt-go-check" build number 533 originally caused by: Started by upstream project "libvirt-go-build" build number 541 originally caused by: 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-debian-9 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/> [libvirt-go] $ /bin/sh -xe /tmp/jenkins6168847707965440858.sh + export TEST_ARGS=-tags api + go test -tags api Missing enum 'VIR_CONNECT_LIST_STORAGE_POOLS_ISCSI_DIRECT' --- FAIL: TestAPICoverage (0.59s) panic: Missing symbols found [recovered] panic: Missing symbols found goroutine 5 [running]: panic(0x55b46b347300, 0xc4201f0730) /usr/lib/go-1.7/src/runtime/panic.go:500 +0x1a1 testing.tRunner.func1(0xc420078180) /usr/lib/go-1.7/src/testing/testing.go:579 +0x25d panic(0x55b46b347300, 0xc4201f0730) /usr/lib/go-1.7/src/runtime/panic.go:458 +0x243 _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/.TestAPICoverage(0xc420078180)> <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/api_test.go>:501 +0x5ff testing.tRunner(0xc420078180, 0x55b46b39aa88) /usr/lib/go-1.7/src/testing/testing.go:610 +0x81 created by testing.(*T).Run /usr/lib/go-1.7/src/testing/testing.go:646 +0x2ec exit status 2 FAIL _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/> 0.808s Build step 'Execute shell' marked build as failure
See <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/534/display/redirect> ------------------------------------------ Started by upstream project "libvirt-go-check" build number 534 originally caused by: Started by upstream project "libvirt-go-build" build number 542 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-debian-9 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/> [libvirt-go] $ /bin/sh -xe /tmp/jenkins1044832705464445928.sh + export TEST_ARGS=-tags api + go test -tags api Missing enum 'VIR_CONNECT_LIST_STORAGE_POOLS_ISCSI_DIRECT' --- FAIL: TestAPICoverage (0.22s) panic: Missing symbols found [recovered] panic: Missing symbols found goroutine 5 [running]: panic(0x5561d78f1300, 0xc42042cc80) /usr/lib/go-1.7/src/runtime/panic.go:500 +0x1a1 testing.tRunner.func1(0xc420078180) /usr/lib/go-1.7/src/testing/testing.go:579 +0x25d panic(0x5561d78f1300, 0xc42042cc80) /usr/lib/go-1.7/src/runtime/panic.go:458 +0x243 _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/.TestAPICoverage(0xc420078180)> <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/api_test.go>:501 +0x5ff testing.tRunner(0xc420078180, 0x5561d7944a88) /usr/lib/go-1.7/src/testing/testing.go:610 +0x81 created by testing.(*T).Run /usr/lib/go-1.7/src/testing/testing.go:646 +0x2ec exit status 2 FAIL _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/> 0.285s Build step 'Execute shell' marked build as failure
See <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/535/display/redirect> ------------------------------------------ Started by upstream project "libvirt-go-check" build number 535 originally caused by: Started by upstream project "libvirt-go-build" build number 543 originally caused by: Started by upstream project "libvirt-build" build number 656 originally caused by: 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-debian-9 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/> [libvirt-go] $ /bin/sh -xe /tmp/jenkins7723990027141939228.sh + export TEST_ARGS=-tags api + go test -tags api Missing enum 'VIR_CONNECT_LIST_STORAGE_POOLS_ISCSI_DIRECT' --- FAIL: TestAPICoverage (0.99s) panic: Missing symbols found [recovered] panic: Missing symbols found goroutine 5 [running]: panic(0x55f9651f1300, 0xc420432890) /usr/lib/go-1.7/src/runtime/panic.go:500 +0x1a1 testing.tRunner.func1(0xc420078180) /usr/lib/go-1.7/src/testing/testing.go:579 +0x25d panic(0x55f9651f1300, 0xc420432890) /usr/lib/go-1.7/src/runtime/panic.go:458 +0x243 _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/.TestAPICoverage(0xc420078180)> <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/api_test.go>:501 +0x5ff testing.tRunner(0xc420078180, 0x55f965244a88) /usr/lib/go-1.7/src/testing/testing.go:610 +0x81 created by testing.(*T).Run /usr/lib/go-1.7/src/testing/testing.go:646 +0x2ec exit status 2 FAIL _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/> 1.164s Build step 'Execute shell' marked build as failure
See <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/536/display/redirect> ------------------------------------------ Started by upstream project "libvirt-go-check" build number 536 originally caused by: Started by upstream project "libvirt-go-build" build number 544 originally caused by: Started by upstream project "libvirt-build" build number 657 originally caused by: 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-debian-9 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/> [libvirt-go] $ /bin/sh -xe /tmp/jenkins3257172345460665131.sh + export TEST_ARGS=-tags api + go test -tags api Missing enum 'VIR_CONNECT_LIST_STORAGE_POOLS_ISCSI_DIRECT' --- FAIL: TestAPICoverage (1.50s) panic: Missing symbols found [recovered] panic: Missing symbols found goroutine 5 [running]: panic(0x5649d1850300, 0xc4204486a0) /usr/lib/go-1.7/src/runtime/panic.go:500 +0x1a1 testing.tRunner.func1(0xc420078180) /usr/lib/go-1.7/src/testing/testing.go:579 +0x25d panic(0x5649d1850300, 0xc4204486a0) /usr/lib/go-1.7/src/runtime/panic.go:458 +0x243 _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/.TestAPICoverage(0xc420078180)> <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/api_test.go>:501 +0x5ff testing.tRunner(0xc420078180, 0x5649d18a3a88) /usr/lib/go-1.7/src/testing/testing.go:610 +0x81 created by testing.(*T).Run /usr/lib/go-1.7/src/testing/testing.go:646 +0x2ec exit status 2 FAIL _<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/> 1.853s Build step 'Execute shell' marked build as failure
participants (1)
-
ci＠centos.org