- CI - libvirt List Archives

[Libvirt-ci] Build failed in Jenkins: libvirt-perl-master-check » libvirt-centos-7 #59
by ci＠centos.org 06 Jun '18

06 Jun '18

See <https://ci.centos.org/job/libvirt-perl-master-check/systems=libvirt-centos-…> ------------------------------------------ Started by upstream project "libvirt-perl-master-check" build number 59 originally caused by: Started by upstream project "libvirt-perl-master-build" build number 1229 originally caused by: Started by upstream project "libvirt-master-build" build number 1495 originally caused by: Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-centos-7 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-master-check/systems=libvirt-centos-…> [libvirt-perl-master] $ /bin/sh -xe /tmp/jenkins5667374088812547013.sh + export TEST_MAINTAINER=1 + TEST_MAINTAINER=1 + perl Build test t/005-pod.t ............ ok t/010-pod-coverage.t ... ok t/015-changes.t ........ ok t/020-constants.t ...... ok # Failed test 'virGetLastErrorCode' # at t/030-api-coverage.t line 159. # Failed test 'virGetLastErrorDomain' # at t/030-api-coverage.t line 159. # Looks like you failed 2 tests of 1619. t/030-api-coverage.t ... Dubious, test returned 2 (wstat 512, 0x200) Failed 2/1619 subtests t/100-connect.t ........ ok t/200-domains.t ........ ok t/300-networks.t ....... ok t/400-storage-pools.t .. ok t/500-storage-vols.t ... ok t/600-interfaces.t ..... ok t/800-events.t ......... ok Test Summary Report ------------------- t/030-api-coverage.t (Wstat: 512 Tests: 1619 Failed: 2) Failed tests: 311-312 Non-zero exit status: 2 Files=12, Tests=1871, 32 wallclock secs ( 0.35 usr 0.05 sys + 7.59 cusr 0.37 csys = 8.36 CPU) Result: FAIL Failed 1/12 test programs. 2/1871 subtests failed. Build step 'Execute shell' marked build as failure

1 5

[Libvirt-ci] Build failed in Jenkins: libvirt-perl-master-check » libvirt-debian-8 #59
by ci＠centos.org 06 Jun '18

06 Jun '18

See <https://ci.centos.org/job/libvirt-perl-master-check/systems=libvirt-debian-…> ------------------------------------------ Started by upstream project "libvirt-perl-master-check" build number 59 originally caused by: Started by upstream project "libvirt-perl-master-build" build number 1229 originally caused by: Started by upstream project "libvirt-master-build" build number 1495 originally caused by: Started by an SCM change 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-perl-master-check/systems=libvirt-debian-…> [libvirt-perl-master] $ /bin/sh -xe /tmp/jenkins311809621843616438.sh + export TEST_MAINTAINER=1 + perl Build test t/005-pod.t ............ ok t/010-pod-coverage.t ... ok t/015-changes.t ........ ok t/020-constants.t ...... ok # Failed test 'virGetLastErrorCode' # at t/030-api-coverage.t line 159. # Failed test 'virGetLastErrorDomain' # at t/030-api-coverage.t line 159. # Looks like you failed 2 tests of 1619. t/030-api-coverage.t ... Dubious, test returned 2 (wstat 512, 0x200) Failed 2/1619 subtests t/100-connect.t ........ ok t/200-domains.t ........ ok t/300-networks.t ....... ok t/400-storage-pools.t .. ok t/500-storage-vols.t ... ok t/600-interfaces.t ..... ok t/800-events.t ......... ok Test Summary Report ------------------- t/030-api-coverage.t (Wstat: 512 Tests: 1619 Failed: 2) Failed tests: 311-312 Non-zero exit status: 2 Files=12, Tests=1871, 33 wallclock secs ( 0.73 usr 0.13 sys + 11.08 cusr 0.89 csys = 12.83 CPU) Result: FAIL Failed 1/12 test programs. 2/1871 subtests failed. Build step 'Execute shell' marked build as failure

1 5

[Libvirt-ci] Build failed in Jenkins: libvirt-python-master-check » libvirt-freebsd-10 #149
by ci＠centos.org 06 Jun '18

06 Jun '18

See <https://ci.centos.org/job/libvirt-python-master-check/systems=libvirt-freeb…> ------------------------------------------ Started by upstream project "libvirt-python-master-check" build number 149 originally caused by: Started by upstream project "libvirt-python-master-build" build number 165 originally caused by: Started by upstream project "libvirt-master-build" build number 1495 originally caused by: Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-freebsd-10 (libvirt) in workspace <https://ci.centos.org/job/libvirt-python-master-check/systems=libvirt-freeb…> [libvirt-python-master] $ /bin/sh -xe /tmp/jenkins1092402296799777441.sh + /usr/local/bin/python3 ./setup.py test running test /usr/local/bin/python3 sanitytest.py build/lib.freebsd-10.4-RELEASE-amd64-3.6 /home/jenkins/build/libvirt/share/libvirt/api/libvirt-api.xml FAIL virGetLastErrorCode -> libvirt.getLastErrorCode (C API not mapped to python) FAIL virGetLastErrorDomain -> libvirt.getLastErrorDomain (C API not mapped to python) FAIL libvirt.virGetLastErrorCode (Python API not mapped to C) FAIL libvirt.virGetLastErrorDomain (Python API not mapped to C) error: command '/usr/local/bin/python3' failed with exit status 1 Build step 'Execute shell' marked build as failure

1 3

[Libvirt-ci] Build failed in Jenkins: libvirt-perl-master-check » libvirt-debian-9 #59
by ci＠centos.org 06 Jun '18

06 Jun '18

See <https://ci.centos.org/job/libvirt-perl-master-check/systems=libvirt-debian-…> ------------------------------------------ Started by upstream project "libvirt-perl-master-check" build number 59 originally caused by: Started by upstream project "libvirt-perl-master-build" build number 1229 originally caused by: Started by upstream project "libvirt-master-build" build number 1495 originally caused by: 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-perl-master-check/systems=libvirt-debian-…> [libvirt-perl-master] $ /bin/sh -xe /tmp/jenkins8860879635037865813.sh + export TEST_MAINTAINER=1 + perl Build test t/005-pod.t ............ ok t/010-pod-coverage.t ... ok t/015-changes.t ........ ok t/020-constants.t ...... ok # Failed test 'virGetLastErrorCode' # at t/030-api-coverage.t line 159. # Failed test 'virGetLastErrorDomain' # at t/030-api-coverage.t line 159. # Looks like you failed 2 tests of 1619. t/030-api-coverage.t ... Dubious, test returned 2 (wstat 512, 0x200) Failed 2/1619 subtests t/100-connect.t ........ ok t/200-domains.t ........ ok t/300-networks.t ....... ok t/400-storage-pools.t .. ok t/500-storage-vols.t ... ok t/600-interfaces.t ..... ok t/800-events.t ......... ok Test Summary Report ------------------- t/030-api-coverage.t (Wstat: 512 Tests: 1619 Failed: 2) Failed tests: 311-312 Non-zero exit status: 2 Files=12, Tests=1871, 21 wallclock secs ( 0.48 usr 0.03 sys + 7.64 cusr 0.40 csys = 8.55 CPU) Result: FAIL Failed 1/12 test programs. 2/1871 subtests failed. Build step 'Execute shell' marked build as failure

1 5

[Libvirt-ci] Build failed in Jenkins: libvirt-python-master-check » libvirt-freebsd-11 #149
by ci＠centos.org 06 Jun '18

06 Jun '18

See <https://ci.centos.org/job/libvirt-python-master-check/systems=libvirt-freeb…> ------------------------------------------ Started by upstream project "libvirt-python-master-check" build number 149 originally caused by: Started by upstream project "libvirt-python-master-build" build number 165 originally caused by: Started by upstream project "libvirt-master-build" build number 1495 originally caused by: Started by an SCM change 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-python-master-check/systems=libvirt-freeb…> [libvirt-python-master] $ /bin/sh -xe /tmp/jenkins3968515169609587243.sh + /usr/local/bin/python3 ./setup.py test running test /usr/local/bin/python3 sanitytest.py build/lib.freebsd-11.1-RELEASE-amd64-3.6 /home/jenkins/build/libvirt/share/libvirt/api/libvirt-api.xml FAIL virGetLastErrorCode -> libvirt.getLastErrorCode (C API not mapped to python) FAIL virGetLastErrorDomain -> libvirt.getLastErrorDomain (C API not mapped to python) FAIL libvirt.virGetLastErrorCode (Python API not mapped to C) FAIL libvirt.virGetLastErrorDomain (Python API not mapped to C) error: command '/usr/local/bin/python3' failed with exit status 1 Build step 'Execute shell' marked build as failure

1 3

[Libvirt-ci] Build failed in Jenkins: libvirt-python-master-check » libvirt-fedora-28 #149
by ci＠centos.org 06 Jun '18

06 Jun '18

See <https://ci.centos.org/job/libvirt-python-master-check/systems=libvirt-fedor…> ------------------------------------------ Started by upstream project "libvirt-python-master-check" build number 149 originally caused by: Started by upstream project "libvirt-python-master-build" build number 165 originally caused by: Started by upstream project "libvirt-master-build" build number 1495 originally caused by: Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-28 (libvirt) in workspace <https://ci.centos.org/job/libvirt-python-master-check/systems=libvirt-fedor…> [libvirt-python-master] $ /bin/sh -xe /tmp/jenkins4970573662882550259.sh + /usr/bin/python3 ./setup.py test running test /usr/bin/python3 sanitytest.py build/lib.linux-x86_64-3.6 /home/jenkins/build/libvirt/share/libvirt/api/libvirt-api.xml FAIL virGetLastErrorCode -> libvirt.getLastErrorCode (C API not mapped to python) FAIL virGetLastErrorDomain -> libvirt.getLastErrorDomain (C API not mapped to python) FAIL libvirt.virGetLastErrorCode (Python API not mapped to C) FAIL libvirt.virGetLastErrorDomain (Python API not mapped to C) error: command '/usr/bin/python3' failed with exit status 1 Build step 'Execute shell' marked build as failure

1 3

[Libvirt-ci] Build failed in Jenkins: libvirt-python-master-check » libvirt-fedora-27 #149
by ci＠centos.org 06 Jun '18

06 Jun '18

See <https://ci.centos.org/job/libvirt-python-master-check/systems=libvirt-fedor…> ------------------------------------------ Started by upstream project "libvirt-python-master-check" build number 149 originally caused by: Started by upstream project "libvirt-python-master-build" build number 165 originally caused by: Started by upstream project "libvirt-master-build" build number 1495 originally caused by: Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-27 (libvirt) in workspace <https://ci.centos.org/job/libvirt-python-master-check/systems=libvirt-fedor…> [libvirt-python-master] $ /bin/sh -xe /tmp/jenkins5638948001811580364.sh + /usr/bin/python3 ./setup.py test running test /usr/bin/python3 sanitytest.py build/lib.linux-x86_64-3.6 /home/jenkins/build/libvirt/share/libvirt/api/libvirt-api.xml FAIL virGetLastErrorCode -> libvirt.getLastErrorCode (C API not mapped to python) FAIL virGetLastErrorDomain -> libvirt.getLastErrorDomain (C API not mapped to python) FAIL libvirt.virGetLastErrorCode (Python API not mapped to C) FAIL libvirt.virGetLastErrorDomain (Python API not mapped to C) error: command '/usr/bin/python3' failed with exit status 1 Build step 'Execute shell' marked build as failure

1 3

[Libvirt-ci] Build failed in Jenkins: libvirt-python-master-check » libvirt-debian-9 #149
by ci＠centos.org 06 Jun '18

06 Jun '18

See <https://ci.centos.org/job/libvirt-python-master-check/systems=libvirt-debia…> ------------------------------------------ Started by upstream project "libvirt-python-master-check" build number 149 originally caused by: Started by upstream project "libvirt-python-master-build" build number 165 originally caused by: Started by upstream project "libvirt-master-build" build number 1495 originally caused by: 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-python-master-check/systems=libvirt-debia…> [libvirt-python-master] $ /bin/sh -xe /tmp/jenkins1944023021752180635.sh + /usr/bin/python3 ./setup.py test running test /usr/bin/python3 sanitytest.py build/lib.linux-x86_64-3.5 /home/jenkins/build/libvirt/share/libvirt/api/libvirt-api.xml FAIL virGetLastErrorCode -> libvirt.getLastErrorCode (C API not mapped to python) FAIL virGetLastErrorDomain -> libvirt.getLastErrorDomain (C API not mapped to python) FAIL libvirt.virGetLastErrorCode (Python API not mapped to C) FAIL libvirt.virGetLastErrorDomain (Python API not mapped to C) error: command '/usr/bin/python3' failed with exit status 1 Build step 'Execute shell' marked build as failure

1 3

[Libvirt-ci] Build failed in Jenkins: libvirt-python-master-check » libvirt-centos-7 #149
by ci＠centos.org 06 Jun '18

06 Jun '18

See <https://ci.centos.org/job/libvirt-python-master-check/systems=libvirt-cento…> ------------------------------------------ Started by upstream project "libvirt-python-master-check" build number 149 originally caused by: Started by upstream project "libvirt-python-master-build" build number 165 originally caused by: Started by upstream project "libvirt-master-build" build number 1495 originally caused by: Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-centos-7 (libvirt) in workspace <https://ci.centos.org/job/libvirt-python-master-check/systems=libvirt-cento…> [libvirt-python-master] $ /bin/sh -xe /tmp/jenkins4896888471986000422.sh + /usr/bin/python2 ./setup.py test running test /usr/bin/python2 sanitytest.py build/lib.linux-x86_64-2.7 /home/jenkins/build/libvirt/share/libvirt/api/libvirt-api.xml FAIL virGetLastErrorCode -> libvirt.getLastErrorCode (C API not mapped to python) FAIL virGetLastErrorDomain -> libvirt.getLastErrorDomain (C API not mapped to python) FAIL libvirt.virGetLastErrorCode (Python API not mapped to C) FAIL libvirt.virGetLastErrorDomain (Python API not mapped to C) error: command '/usr/bin/python2' failed with exit status 1 Build step 'Execute shell' marked build as failure

1 3

[Libvirt-ci] Build failed in Jenkins: libvirt-python-master-check » libvirt-debian-8 #149
by ci＠centos.org 06 Jun '18

06 Jun '18

See <https://ci.centos.org/job/libvirt-python-master-check/systems=libvirt-debia…> ------------------------------------------ Started by upstream project "libvirt-python-master-check" build number 149 originally caused by: Started by upstream project "libvirt-python-master-build" build number 165 originally caused by: Started by upstream project "libvirt-master-build" build number 1495 originally caused by: Started by an SCM change 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-python-master-check/systems=libvirt-debia…> [libvirt-python-master] $ /bin/sh -xe /tmp/jenkins6464552250210722915.sh + /usr/bin/python3 ./setup.py test running test /usr/bin/python3 sanitytest.py build/lib.linux-x86_64-3.4 /home/jenkins/build/libvirt/share/libvirt/api/libvirt-api.xml FAIL virGetLastErrorCode -> libvirt.getLastErrorCode (C API not mapped to python) FAIL virGetLastErrorDomain -> libvirt.getLastErrorDomain (C API not mapped to python) FAIL libvirt.virGetLastErrorCode (Python API not mapped to C) FAIL libvirt.virGetLastErrorDomain (Python API not mapped to C) error: command '/usr/bin/python3' failed with exit status 1 Build step 'Execute shell' marked build as failure

1 3