[Libvirt-ci] Build failed in Jenkins: virt-manager-master-check » libvirt-fedora-rawhide #326 - CI

[Libvirt-ci] Build failed in Jenkins: virt-manager-master-check » libvirt-fedora-rawhide #326

ci＠centos.org

6 Aug 2018 6 Aug '18

8:31 a.m.

See <https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-fedora-rawhide/326/display/redirect> ------------------------------------------ Started by upstream project "virt-manager-master-check" build number 326 originally caused by: Started by upstream project "virt-manager-master-build" build number 327 originally caused by: Started by upstream project "libvirt-python-master-build" build number 315 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-fedora-rawhide (libvirt) in workspace <https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-fedora-rawhide/ws/> [virt-manager-master] $ /bin/sh -xe /tmp/jenkins308991356718643071.sh + /usr/bin/python3 ./setup.py test running test Traceback (most recent call last): File "/home/jenkins/build/libvirt/lib64/python3.6/site-packages/libvirt.py", line 24, in <module> import cygvirtmod as libvirtmod ModuleNotFoundError: No module named 'cygvirtmod' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "./setup.py", line 726, in <module> distclass=VMMDistribution, File "/usr/lib64/python3.7/distutils/core.py", line 148, in setup dist.run_commands() File "/usr/lib64/python3.7/distutils/dist.py", line 966, in run_commands self.run_command(cmd) File "/usr/lib64/python3.7/distutils/dist.py", line 985, in run_command cmd_obj.run() File "./setup.py", line 524, in run TestBaseCommand.run(self) File "./setup.py", line 440, in run import tests as testsmodule File "<https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-fedora-rawhide/ws/tests/__init__.py",> line 19, in <module> from tests import utils File "<https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-fedora-rawhide/ws/tests/utils.py",> line 11, in <module> import libvirt File "/home/jenkins/build/libvirt/lib64/python3.6/site-packages/libvirt.py", line 28, in <module> raise lib_e File "/home/jenkins/build/libvirt/lib64/python3.6/site-packages/libvirt.py", line 20, in <module> import libvirtmod ModuleNotFoundError: No module named 'libvirtmod' Build step 'Execute shell' marked build as failure

Show replies by date

ci＠centos.org

6 Aug 6 Aug

8:58 a.m.

New subject: [Libvirt-ci] Build failed in Jenkins: virt-manager-master-check » libvirt-fedora-rawhide #327

See <https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-fedora-rawhide/327/display/redirect> ------------------------------------------ Started by upstream project "virt-manager-master-check" build number 327 originally caused by: Started by upstream project "virt-manager-master-build" build number 328 originally caused by: Started by upstream project "libvirt-python-master-build" build number 316 originally caused by: Started by upstream project "libvirt-master-build" build number 1649 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/virt-manager-master-check/systems=libvirt-fedora-rawhide/ws/> [virt-manager-master] $ /bin/sh -xe /tmp/jenkins8474699378252128089.sh + /usr/bin/python3 ./setup.py test running test Traceback (most recent call last): File "/home/jenkins/build/libvirt/lib64/python3.6/site-packages/libvirt.py", line 24, in <module> import cygvirtmod as libvirtmod ModuleNotFoundError: No module named 'cygvirtmod' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "./setup.py", line 726, in <module> distclass=VMMDistribution, File "/usr/lib64/python3.7/distutils/core.py", line 148, in setup dist.run_commands() File "/usr/lib64/python3.7/distutils/dist.py", line 966, in run_commands self.run_command(cmd) File "/usr/lib64/python3.7/distutils/dist.py", line 985, in run_command cmd_obj.run() File "./setup.py", line 524, in run TestBaseCommand.run(self) File "./setup.py", line 440, in run import tests as testsmodule File "<https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-fedora-rawhide/ws/tests/__init__.py",> line 19, in <module> from tests import utils File "<https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-fedora-rawhide/ws/tests/utils.py",> line 11, in <module> import libvirt File "/home/jenkins/build/libvirt/lib64/python3.6/site-packages/libvirt.py", line 28, in <module> raise lib_e File "/home/jenkins/build/libvirt/lib64/python3.6/site-packages/libvirt.py", line 20, in <module> import libvirtmod ModuleNotFoundError: No module named 'libvirtmod' Build step 'Execute shell' marked build as failure

ci＠centos.org

10:37 a.m.

New subject: [Libvirt-ci] Build failed in Jenkins: virt-manager-master-check » libvirt-fedora-rawhide #328

See <https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-fedora-rawhide/328/display/redirect> ------------------------------------------ [...truncated 4.71 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 [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-rawhide (libvirt) in workspace <https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-fedora-rawhide/ws/> [virt-manager-master] $ /bin/sh -xe /tmp/jenkins8252735305520317727.sh + /usr/bin/python3 ./setup.py test running test Traceback (most recent call last): File "/home/jenkins/build/libvirt/lib64/python3.6/site-packages/libvirt.py", line 24, in <module> import cygvirtmod as libvirtmod ModuleNotFoundError: No module named 'cygvirtmod' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "./setup.py", line 726, in <module> distclass=VMMDistribution, File "/usr/lib64/python3.7/distutils/core.py", line 148, in setup dist.run_commands() File "/usr/lib64/python3.7/distutils/dist.py", line 966, in run_commands self.run_command(cmd) File "/usr/lib64/python3.7/distutils/dist.py", line 985, in run_command cmd_obj.run() File "./setup.py", line 524, in run TestBaseCommand.run(self) File "./setup.py", line 440, in run import tests as testsmodule File "<https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-fedora-rawhide/ws/tests/__init__.py",> line 19, in <module> from tests import utils File "<https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-fedora-rawhide/ws/tests/utils.py",> line 11, in <module> import libvirt File "/home/jenkins/build/libvirt/lib64/python3.6/site-packages/libvirt.py", line 28, in <module> raise lib_e File "/home/jenkins/build/libvirt/lib64/python3.6/site-packages/libvirt.py", line 20, in <module> import libvirtmod ModuleNotFoundError: No module named 'libvirtmod' Build step 'Execute shell' marked build as failure

ci＠centos.org

11:45 a.m.

New subject: [Libvirt-ci] Build failed in Jenkins: virt-manager-master-check » libvirt-fedora-rawhide #329

See <https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-fedora-rawhide/329/display/redirect> ------------------------------------------ Started by upstream project "virt-manager-master-check" build number 329 originally caused by: Started by upstream project "virt-manager-master-build" build number 330 originally caused by: Started by upstream project "libvirt-python-master-build" build number 318 originally caused by: Started by upstream project "libvirt-master-build" build number 1651 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 [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-rawhide (libvirt) in workspace <https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-fedora-rawhide/ws/> [virt-manager-master] $ /bin/sh -xe /tmp/jenkins7418511675485098288.sh + /usr/bin/python3 ./setup.py test running test Traceback (most recent call last): File "/home/jenkins/build/libvirt/lib64/python3.6/site-packages/libvirt.py", line 24, in <module> import cygvirtmod as libvirtmod ModuleNotFoundError: No module named 'cygvirtmod' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "./setup.py", line 726, in <module> distclass=VMMDistribution, File "/usr/lib64/python3.7/distutils/core.py", line 148, in setup dist.run_commands() File "/usr/lib64/python3.7/distutils/dist.py", line 966, in run_commands self.run_command(cmd) File "/usr/lib64/python3.7/distutils/dist.py", line 985, in run_command cmd_obj.run() File "./setup.py", line 524, in run TestBaseCommand.run(self) File "./setup.py", line 440, in run import tests as testsmodule File "<https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-fedora-rawhide/ws/tests/__init__.py",> line 19, in <module> from tests import utils File "<https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-fedora-rawhide/ws/tests/utils.py",> line 11, in <module> import libvirt File "/home/jenkins/build/libvirt/lib64/python3.6/site-packages/libvirt.py", line 28, in <module> raise lib_e File "/home/jenkins/build/libvirt/lib64/python3.6/site-packages/libvirt.py", line 20, in <module> import libvirtmod ModuleNotFoundError: No module named 'libvirtmod' Build step 'Execute shell' marked build as failure

ci＠centos.org

7 Aug 7 Aug

10:35 a.m.

New subject: [Libvirt-ci] Build failed in Jenkins: virt-manager-master-check » libvirt-fedora-rawhide #330

See <https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-fedora-rawhide/330/display/redirect> ------------------------------------------ Started by upstream project "virt-manager-master-check" build number 330 originally caused by: Started by upstream project "virt-manager-master-build" build number 331 originally caused by: Started by upstream project "libvirt-python-master-build" build number 319 originally caused by: Started by upstream project "libvirt-master-build" build number 1652 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/virt-manager-master-check/systems=libvirt-fedora-rawhide/ws/> [virt-manager-master] $ /bin/sh -xe /tmp/jenkins767552038009630043.sh + /usr/bin/python3 ./setup.py test running test Traceback (most recent call last): File "/home/jenkins/build/libvirt/lib64/python3.6/site-packages/libvirt.py", line 24, in <module> import cygvirtmod as libvirtmod ModuleNotFoundError: No module named 'cygvirtmod' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "./setup.py", line 726, in <module> distclass=VMMDistribution, File "/usr/lib64/python3.7/distutils/core.py", line 148, in setup dist.run_commands() File "/usr/lib64/python3.7/distutils/dist.py", line 966, in run_commands self.run_command(cmd) File "/usr/lib64/python3.7/distutils/dist.py", line 985, in run_command cmd_obj.run() File "./setup.py", line 524, in run TestBaseCommand.run(self) File "./setup.py", line 440, in run import tests as testsmodule File "<https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-fedora-rawhide/ws/tests/__init__.py",> line 19, in <module> from tests import utils File "<https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-fedora-rawhide/ws/tests/utils.py",> line 11, in <module> import libvirt File "/home/jenkins/build/libvirt/lib64/python3.6/site-packages/libvirt.py", line 28, in <module> raise lib_e File "/home/jenkins/build/libvirt/lib64/python3.6/site-packages/libvirt.py", line 20, in <module> import libvirtmod ModuleNotFoundError: No module named 'libvirtmod' Build step 'Execute shell' marked build as failure

ci＠centos.org

8 Aug 8 Aug

5:31 a.m.

New subject: [Libvirt-ci] Jenkins build is back to normal : virt-manager-master-check » libvirt-fedora-rawhide #331

See <https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-fedora-rawhide/331/display/redirect>

2590

Age (days ago)

2592

Last active (days ago)

List overview

Download

5 comments

1 participants

participants (1)

ci＠centos.org