New subject: [Libvirt-ci] Jenkins build is back to normal : libvirt-python-build » libvirt-centos-7 #853

Wednesday, 27 November 2019

See
<https://ci.centos.org/job/libvirt-python-build/systems=libvirt-centos-7/8...

------------------------------------------
[...truncated 19.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
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on libvirt-centos-7 (libvirt) in workspace
<https://ci.centos.org/job/libvirt-python-build/systems=libvirt-centos-7/w...
No credentials specified
...
 git rev-parse --is-inside-work-tree # timeout=10 Fetching
changes from the remote Git repository
...
 git config remote.origin.url
https://github.com/libvirt/libvirt-python.git # timeout=10 Fetching upstream changes
from https://github.com/libvirt/libvirt-python.git
...
 git --version # timeout=10
 git fetch --tags --progress https://github.com/libvirt/libvirt-python.git
+refs/heads/*:refs/remotes/origin/* Checking out Revision
1236ff5386c19f04de593bdc40dd14a5c0cc4926 (refs/remotes/origin/master)
...
 git config core.sparsecheckout # timeout=10
 git checkout -f 1236ff5386c19f04de593bdc40dd14a5c0cc4926 Commit message:
"Release of libvirt-python 5.9.0"
...
 git rev-list --no-walk 1236ff5386c19f04de593bdc40dd14a5c0cc4926 #
timeout=10 Cleaning workspace
...
 git rev-parse --verify HEAD # timeout=10 Resetting working
tree
...
 git reset --hard # timeout=10
 git clean -fdx # timeout=10 [libvirt-python] $ /bin/sh -xe
/tmp/jenkins14944560796490341733.sh
+ /usr/bin/python2 ./setup.py build
running build
/usr/bin/pkg-config --print-errors --atleast-version=0.9.11 libvirt
/usr/bin/python2 generator.py libvirt
/home/jenkins/build/libvirt/share/libvirt/api/libvirt-api.xml
Found 476 functions in /home/jenkins/build/libvirt/share/libvirt/api/libvirt-api.xml
Found 0 functions in libvirt-override-api.xml
Generated 387 wrapper functions
/usr/bin/python2 generator.py libvirt-qemu
/home/jenkins/build/libvirt/share/libvirt/api/libvirt-qemu-api.xml
Found 5 functions in /home/jenkins/build/libvirt/share/libvirt/api/libvirt-qemu-api.xml
Found 0 functions in libvirt-qemu-override-api.xml
Generated 3 wrapper functions
Traceback (most recent call last):
  File "generator.py", line 2143, in <module>
    qemuBuildWrappers(sys.argv[1])
  File "generator.py", line 2008, in qemuBuildWrappers
    items.sort(key=lambda i: (int(i[1]), i[0]))
  File "generator.py", line 2008, in <lambda>
    items.sort(key=lambda i: (int(i[1]), i[0]))
ValueError: invalid literal for int() with base 10:
'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_BLOCK'
error: command '/usr/bin/python2' failed with exit status 1
Build step 'Execute shell' marked build as failure

2024

2023

2022

2021

2020

2019

2018

2017

2016

[Libvirt-ci] Build failed in Jenkins: libvirt-python-build » libvirt-centos-7 #852