[Libvirt-ci] Build failed in Jenkins: libvirt-go-check » libvirt-debian-9 #821

ci at centos.org ci at centos.org
Wed Nov 27 18:44:42 UTC 2019 

See <https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/821/display/redirect>

------------------------------------------
[...truncated 20.24 KB...]
   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
   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/jenkins3324809033471413137.sh
+ export TEST_ARGS=-tags api
+ go test -tags api
Missing function 'virDomainAgentSetResponseTimeout'
Missing enum 'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_BLOCK'
Missing enum 'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_DEFAULT'
Missing enum 'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_NOWAIT'
Missing enum 'VIR_FROM_BPF'
--- FAIL: TestAPICoverage (0.50s)
panic: Missing symbols found [recovered]
	panic: Missing symbols found

goroutine 19 [running]:
panic(0x555fb6e80dc0, 0xc42043d110)
	/usr/lib/go-1.7/src/runtime/panic.go:500 +0x1a1
testing.tRunner.func1(0xc420088180)
	/usr/lib/go-1.7/src/testing/testing.go:579 +0x25d
panic(0x555fb6e80dc0, 0xc42043d110)
	/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(0xc420088180)>
	<https://ci.centos.org/job/libvirt-go-check/systems=libvirt-debian-9/ws/api_test.go>:503 +0x5ff
testing.tRunner(0xc420088180, 0x555fb6ed45e8)
	/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.573s
Build step 'Execute shell' marked build as failure

More information about the Libvirt-ci mailing list