libvirt List Archives
Sign In Sign Up
Manage this list Sign In Sign Up

Keyboard Shortcuts

Thread View

  • j: Next unread message
  • k: Previous unread message
  • j a: Jump to all threads
  • j l: Jump to MailingList overview

CI

Thread Start a new thread
Download
Threads by month
  • ----- 2025 -----
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2024 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2023 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2022 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2021 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2020 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2019 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2018 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2017 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2016 -----
  • December
  • November
  • October
  • September
  • August
  • July
ci@lists.libvirt.org

April 2019

  • 2 participants
  • 96 discussions
[Libvirt-ci] Build failed in Jenkins: virt-manager-check » libvirt-debian-9 #636
by ci@centos.org 13 Apr '19

13 Apr '19
See <https://ci.centos.org/job/virt-manager-check/systems=libvirt-debian-9/636/d…> ------------------------------------------ Started by upstream project "virt-manager-check" build number 636 originally caused by: Started by upstream project "virt-manager-build" build number 639 originally caused by: Started by upstream project "libvirt-python-build" build number 386 originally caused by: Started by upstream project "libvirt-build" build number 472 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-debian-9 (libvirt) in workspace <https://ci.centos.org/job/virt-manager-check/systems=libvirt-debian-9/ws/> [virt-manager] $ /bin/sh -xe /tmp/jenkins6090044919285261988.sh + /usr/bin/python3 ./setup.py test running test .........................................................................................................I/O warning : failed to load external entity "/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml" .......................................F..............................................................................................................................................................................................................................................................................................................................................sssssssssssssssssss ====================================================================== FAIL: testCLI0018virt_install_cpu_rhel7_default (tests.clitest.CLITests) ---------------------------------------------------------------------- Traceback (most recent call last): File "<https://ci.centos.org/job/virt-manager-check/systems=libvirt-debian-9/ws/te…",> line 1209, in <lambda> return lambda s: cmdtemplate(s, cmd) File "<https://ci.centos.org/job/virt-manager-check/systems=libvirt-debian-9/ws/te…",> line 1208, in cmdtemplate _cmdobj.run(self) File "<https://ci.centos.org/job/virt-manager-check/systems=libvirt-debian-9/ws/te…",> line 269, in run tests.fail(err) AssertionError: ./virt-install --name foobar --ram 64 --print-step all --hvm --nographics --noautoconsole --nodisks --pxe --connect __virtinst_test__test://<https://ci.centos.org/job/virt-manager-check/systems=libvirt-debian-9/ws/te…> Conversion outputs did not match. --- tests/cli-test-xml/compare/virt-install-cpu-rhel7-default.xml +++ Generated Output @@ -14,8 +14,6 @@ </features> <cpu mode="custom" match="exact"> <model>Skylake-Client-IBRS</model> - <feature policy="require" name="spec-ctrl"/> - <feature policy="require" name="ssbd"/> </cpu> <clock offset="utc"> <timer name="rtc" tickpolicy="catchup"/> @@ -63,8 +61,6 @@ </features> <cpu mode="custom" match="exact"> <model>Skylake-Client-IBRS</model> - <feature policy="require" name="spec-ctrl"/> - <feature policy="require" name="ssbd"/> </cpu> <clock offset="utc"> <timer name="rtc" tickpolicy="catchup"/> ---------------------------------------------------------------------- Ran 498 tests in 46.678s FAILED (failures=1, skipped=19) Build step 'Execute shell' marked build as failure
1 2
0 0
[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-fedora-rawhide #383
by ci@centos.org 13 Apr '19

13 Apr '19
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-rawhide…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 383 originally caused by: Started by upstream project "libvirt-perl-build" build number 384 originally caused by: Started by upstream project "libvirt-build" build number 472 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/libvirt-perl-check/systems=libvirt-fedora-rawhide…> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins5927694276280101092.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 t/030-api-coverage.t ... ok I/O warning : failed to load external entity "/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml" libvirt error code: 27, message: XML error: failed to parse xml document '/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml' # Looks like your test exited with 2 just after 24. t/100-connect.t ........ Dubious, test returned 2 (wstat 512, 0x200) Failed 1/25 subtests (less 1 skipped subtest: 23 okay) 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/100-connect.t (Wstat: 512 Tests: 24 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 25 tests but ran 24. Files=12, Tests=1913, 78 wallclock secs ( 0.56 usr 0.19 sys + 10.08 cusr 2.49 csys = 13.32 CPU) Result: FAIL Failed 1/12 test programs. 0/1913 subtests failed. Build step 'Execute shell' marked build as failure
1 2
0 0
[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-debian-9 #383
by ci@centos.org 13 Apr '19

13 Apr '19
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-debian-9/383/d…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 383 originally caused by: Started by upstream project "libvirt-perl-build" build number 384 originally caused by: Started by upstream project "libvirt-build" build number 472 originally caused by: 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-check/systems=libvirt-debian-9/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins6594927893069111220.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 t/030-api-coverage.t ... ok I/O warning : failed to load external entity "/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml" libvirt error code: 27, message: XML error: failed to parse xml document '/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml' # Looks like you planned 25 tests but ran 24. # Looks like your test exited with 2 just after 24. t/100-connect.t ........ Dubious, test returned 2 (wstat 512, 0x200) Failed 1/25 subtests (less 1 skipped subtest: 23 okay) 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/100-connect.t (Wstat: 512 Tests: 24 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 25 tests but ran 24. Files=12, Tests=1913, 29 wallclock secs ( 0.52 usr 0.07 sys + 8.89 cusr 0.52 csys = 10.00 CPU) Result: FAIL Failed 1/12 test programs. 0/1913 subtests failed. Build step 'Execute shell' marked build as failure
1 2
0 0
[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-fedora-28 #383
by ci@centos.org 13 Apr '19

13 Apr '19
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-28/383/…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 383 originally caused by: Started by upstream project "libvirt-perl-build" build number 384 originally caused by: Started by upstream project "libvirt-build" build number 472 originally caused by: 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-perl-check/systems=libvirt-fedora-28/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins7893994120516352858.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 t/030-api-coverage.t ... ok I/O warning : failed to load external entity "/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml" libvirt error code: 27, message: XML error: failed to parse xml document '/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml' # Looks like your test exited with 2 just after 24. t/100-connect.t ........ Dubious, test returned 2 (wstat 512, 0x200) Failed 1/25 subtests (less 1 skipped subtest: 23 okay) 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/100-connect.t (Wstat: 512 Tests: 24 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 25 tests but ran 24. Files=12, Tests=1913, 42 wallclock secs ( 0.51 usr 0.06 sys + 8.84 cusr 0.65 csys = 10.06 CPU) Result: FAIL Failed 1/12 test programs. 0/1913 subtests failed. Build step 'Execute shell' marked build as failure
1 2
0 0
[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-fedora-29 #383
by ci@centos.org 13 Apr '19

13 Apr '19
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-29/383/…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 383 originally caused by: Started by upstream project "libvirt-perl-build" build number 384 originally caused by: Started by upstream project "libvirt-build" build number 472 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-fedora-29 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-29/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins216237992003344651.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 t/030-api-coverage.t ... ok I/O warning : failed to load external entity "/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml" libvirt error code: 27, message: XML error: failed to parse xml document '/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml' # Looks like your test exited with 2 just after 24. t/100-connect.t ........ Dubious, test returned 2 (wstat 512, 0x200) Failed 1/25 subtests (less 1 skipped subtest: 23 okay) 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/100-connect.t (Wstat: 512 Tests: 24 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 25 tests but ran 24. Files=12, Tests=1913, 37 wallclock secs ( 0.44 usr 0.07 sys + 8.72 cusr 0.69 csys = 9.92 CPU) Result: FAIL Failed 1/12 test programs. 0/1913 subtests failed. Build step 'Execute shell' marked build as failure
1 2
0 0
[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-freebsd-11 #383
by ci@centos.org 13 Apr '19

13 Apr '19
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-11/383…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 383 originally caused by: Started by upstream project "libvirt-perl-build" build number 384 originally caused by: Started by upstream project "libvirt-build" build number 472 originally caused by: 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-perl-check/systems=libvirt-freebsd-11/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins3082535883974409239.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 t/030-api-coverage.t ... ok I/O warning : failed to load external entity "/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml" libvirt error code: 27, message: XML error: failed to parse xml document '/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml' # Looks like your test exited with 2 just after 24. t/100-connect.t ........ Dubious, test returned 2 (wstat 512, 0x200) Failed 1/25 subtests (less 1 skipped subtest: 23 okay) 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/100-connect.t (Wstat: 512 Tests: 24 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 25 tests but ran 24. Files=12, Tests=1913, 18 wallclock secs ( 0.45 usr 0.28 sys + 13.35 cusr 1.91 csys = 15.98 CPU) Result: FAIL Failed 1/12 test programs. 0/1913 subtests failed. Build step 'Execute shell' marked build as failure
1 2
0 0
[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-centos-7 #383
by ci@centos.org 13 Apr '19

13 Apr '19
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-centos-7/383/d…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 383 originally caused by: Started by upstream project "libvirt-perl-build" build number 384 originally caused by: Started by upstream project "libvirt-build" build number 472 originally caused by: 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-check/systems=libvirt-centos-7/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins633614554182094200.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 t/030-api-coverage.t ... ok I/O warning : failed to load external entity "/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml" libvirt error code: 27, message: XML error: failed to parse xml document '/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml' # Looks like you planned 25 tests but ran 24. # Looks like your test exited with 2 just after 24. t/100-connect.t ........ Dubious, test returned 2 (wstat 512, 0x200) Failed 1/25 subtests (less 1 skipped subtest: 23 okay) 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/100-connect.t (Wstat: 512 Tests: 24 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 25 tests but ran 24. Files=12, Tests=1913, 27 wallclock secs ( 0.47 usr 0.05 sys + 8.34 cusr 0.41 csys = 9.27 CPU) Result: FAIL Failed 1/12 test programs. 0/1913 subtests failed. Build step 'Execute shell' marked build as failure
1 2
0 0
[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-freebsd-12 #383
by ci@centos.org 13 Apr '19

13 Apr '19
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-12/383…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 383 originally caused by: Started by upstream project "libvirt-perl-build" build number 384 originally caused by: Started by upstream project "libvirt-build" build number 472 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-freebsd-12 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-12/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins3072874881024456584.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 t/030-api-coverage.t ... ok I/O warning : failed to load external entity "/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml" libvirt error code: 27, message: XML error: failed to parse xml document '/home/jenkins/build/libvirt/share/libvirt/cpu_map/x86_Cascadelake-Server.xml' # Looks like your test exited with 2 just after 24. t/100-connect.t ........ Dubious, test returned 2 (wstat 512, 0x200) Failed 1/25 subtests (less 1 skipped subtest: 23 okay) 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/100-connect.t (Wstat: 512 Tests: 24 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 25 tests but ran 24. Files=12, Tests=1913, 20 wallclock secs ( 0.59 usr 0.23 sys + 14.73 cusr 1.55 csys = 17.10 CPU) Result: FAIL Failed 1/12 test programs. 0/1913 subtests failed. Build step 'Execute shell' marked build as failure
1 2
0 0
[Libvirt-ci] Still Failing: libvirt/libvirt#2233 (master - 4a0f604)
by Travis CI 13 Apr '19

13 Apr '19
Build Update for libvirt/libvirt ------------------------------------- Build: #2233 Status: Still Failing Duration: 21 mins and 39 secs Commit: 4a0f604 (master) Author: Michal Privoznik Message: cpu_map: Distribute x86_Cascadelake-Server.xml In 2878278c74cc4 we've added new cpu model but we've forgot to distribute the XML file it comes in. Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/673f805d4df2...4a0f604dd031 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/519740411?utm_medium=notificat… -- You can unsubscribe from build emails from the libvirt/libvirt repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=4872032&ut…. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notificati…. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
1 0
0 0
[Libvirt-ci] Still Failing: libvirt/libvirt#2232 (master - 673f805)
by Travis CI 12 Apr '19

12 Apr '19
Build Update for libvirt/libvirt ------------------------------------- Build: #2232 Status: Still Failing Duration: 24 mins and 31 secs Commit: 673f805 (master) Author: Martin Kletzander Message: qemu: Label uniqDir when probing capabilities This does not cause a problem in usual scenarios thanks to us allowing CAP_DAC_OVERRIDE for the qemu process, however in some scenarios this might be an issue because the directory is created with mkdtemp(3) which explicitly creates that with 0700 permissions and qemu running as non-root cannot access that. The scenarios include: - Builds without CAPNG - Running libvirtd in certain container configurations [1] - and possibly others. [1] https://github.com/kubevirt/kubevirt/pull/2181#issuecomment-481840304 Signed-off-by: Martin Kletzander <mkletzan(a)redhat.com> Reviewed-by: Daniel P. Berrangé <berrange(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/df4b46737f43...673f805d4df2 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/519495492?utm_medium=notificat… -- You can unsubscribe from build emails from the libvirt/libvirt repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=4872032&ut…. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notificati…. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
1 0
0 0
  • ← Newer
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • Older →

HyperKitty Powered by HyperKitty version 1.3.12.