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
  • ----- 2026 -----
  • March
  • February
  • January
  • ----- 2025 -----
  • December
  • November
  • October
  • 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

  • 2 participants
  • 9422 discussions
[Libvirt-ci] Still Failing: libvirt/libvirt#2017 (master - 4b23f18)
by Travis CI 15 Feb '19

15 Feb '19
Build Update for libvirt/libvirt ------------------------------------- Build: #2017 Status: Still Failing Duration: 27 mins and 39 secs Commit: 4b23f18 (master) Author: Michal Privoznik Message: qemu_hotplug: Initialize @charAlias in qemuDomainRemoveChrDevice My change in 112f3a8d0f32 was too drastic. The @charAlias variable is initialized only if @monitor == true. However, it is used even outside of that condition, at which point it's just uninitialized pointer. Reported-by: John Ferlan <jferlan(a)redhat.com> Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> Reviewed-by: John Ferlan <jferlan(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/4c4ff7a1a008...4b23f18d2c9e View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/493266739?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#2016 (master - 4c4ff7a)
by Travis CI 15 Feb '19

15 Feb '19
Build Update for libvirt/libvirt ------------------------------------- Build: #2016 Status: Still Failing Duration: 25 mins and 36 secs Commit: 4c4ff7a (master) Author: Marc Hartmayer Message: udev: only report a warning if udev_enumerate_scan_devices fails Even if an error is reported by `udev_enumerate_scan_devices`, e.g. because a driver of a device has an bug, we can still enumerate all other devices. Additionally the documentation of udev_enumerate_scan_devices says that on success an integer >= 0 is returned (see man udev_enumerate_scan_devices(3)). Reviewed-by: Bjoern Walk <bwalk(a)linux.ibm.com> Signed-off-by: Marc Hartmayer <mhartmay(a)linux.ibm.com> Reviewed-by: John Ferlan <jferlan(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/0f110d5ac869...4c4ff7a1a008 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/493252810?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] Broken: libvirt/libvirt#2015 (master - 0f110d5)
by Travis CI 15 Feb '19

15 Feb '19
Build Update for libvirt/libvirt ------------------------------------- Build: #2015 Status: Broken Duration: 42 mins and 24 secs Commit: 0f110d5 (master) Author: Ján Tomko Message: Use NULLSTR_EMPTY Instead of repetitive: s ? s : "" use NULLSTR_EMPTY. Signed-off-by: Ján Tomko <jtomko(a)redhat.com> Reviewed-by: Andrea Bolognani <abologna(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/5657e22212c5...0f110d5ac869 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/493232534?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] Broken: libvirt/libvirt#2014 (master - 5657e22)
by Travis CI 14 Feb '19

14 Feb '19
Build Update for libvirt/libvirt ------------------------------------- Build: #2014 Status: Broken Duration: 21 mins and 30 secs Commit: 5657e22 (master) Author: Michal Privoznik Message: qemu_hotplug: Assume chardev alias always exists in qemuDomainDetachChrDevice The @tmpChr is looked up in domain definition based on user provided chardev XML. Therefore, the alias must have been allocated already when domain was started up. Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> Reviewed-by: John Ferlan <jferlan(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/17ddfd420a0d...5657e22212c5 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/493226157?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] Build failed in Jenkins: libvirt-perl-check » libvirt-freebsd-12 #236
by ci@centos.org 12 Feb '19

12 Feb '19
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-12/236…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 236 originally caused by: Started by upstream project "libvirt-perl-build" build number 236 originally caused by: Started by upstream project "libvirt-build" build number 295 originally caused by: 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-freebsd-12 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-12/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins5491318554996449556.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 'VIR_DOMAIN_MIGRATE_MAX_SPEED_POSTCOPY' # at t/030-api-coverage.t line 175. # Failed test 'VIR_MIGRATE_PARAM_BANDWIDTH_POSTCOPY' # at t/030-api-coverage.t line 219. # Looks like you failed 2 tests of 1650. t/030-api-coverage.t ... Dubious, test returned 2 (wstat 512, 0x200) Failed 2/1650 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: 1650 Failed: 2) Failed tests: 866, 1575 Non-zero exit status: 2 Files=12, Tests=1904, 48 wallclock secs ( 0.97 usr 0.34 sys + 17.75 cusr 1.91 csys = 20.97 CPU) Result: FAIL Failed 1/12 test programs. 2/1904 subtests failed. Build step 'Execute shell' marked build as failure
1 8
0 0
[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-fedora-rawhide #236
by ci@centos.org 12 Feb '19

12 Feb '19
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-rawhide…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 236 originally caused by: Started by upstream project "libvirt-perl-build" build number 236 originally caused by: Started by upstream project "libvirt-build" build number 295 originally caused by: 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/libvirt-perl-check/systems=libvirt-fedora-rawhide…> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins4050725373873540698.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 'VIR_DOMAIN_MIGRATE_MAX_SPEED_POSTCOPY' # at t/030-api-coverage.t line 175. # Failed test 'VIR_MIGRATE_PARAM_BANDWIDTH_POSTCOPY' # at t/030-api-coverage.t line 219. # Looks like you failed 2 tests of 1650. t/030-api-coverage.t ... Dubious, test returned 2 (wstat 512, 0x200) Failed 2/1650 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: 1650 Failed: 2) Failed tests: 866, 1575 Non-zero exit status: 2 Files=12, Tests=1904, 85 wallclock secs ( 0.60 usr 0.14 sys + 10.41 cusr 2.34 csys = 13.49 CPU) Result: FAIL Failed 1/12 test programs. 2/1904 subtests failed. Build step 'Execute shell' marked build as failure
1 8
0 0
[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-freebsd-11 #236
by ci@centos.org 12 Feb '19

12 Feb '19
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-11/236…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 236 originally caused by: Started by upstream project "libvirt-perl-build" build number 236 originally caused by: Started by upstream project "libvirt-build" build number 295 originally caused by: 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-freebsd-11 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-freebsd-11/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins3603046615694462153.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 'VIR_DOMAIN_MIGRATE_MAX_SPEED_POSTCOPY' # at t/030-api-coverage.t line 175. # Failed test 'VIR_MIGRATE_PARAM_BANDWIDTH_POSTCOPY' # at t/030-api-coverage.t line 219. # Looks like you failed 2 tests of 1650. t/030-api-coverage.t ... Dubious, test returned 2 (wstat 512, 0x200) Failed 2/1650 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: 1650 Failed: 2) Failed tests: 866, 1575 Non-zero exit status: 2 Files=12, Tests=1904, 58 wallclock secs ( 0.85 usr 0.35 sys + 17.86 cusr 1.71 csys = 20.77 CPU) Result: FAIL Failed 1/12 test programs. 2/1904 subtests failed. Build step 'Execute shell' marked build as failure
1 8
0 0
[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-fedora-28 #236
by ci@centos.org 12 Feb '19

12 Feb '19
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-28/236/…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 236 originally caused by: Started by upstream project "libvirt-perl-build" build number 236 originally caused by: Started by upstream project "libvirt-build" build number 295 originally caused by: 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-28 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-28/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins7467223510292954283.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 'VIR_DOMAIN_MIGRATE_MAX_SPEED_POSTCOPY' # at t/030-api-coverage.t line 175. # Failed test 'VIR_MIGRATE_PARAM_BANDWIDTH_POSTCOPY' # at t/030-api-coverage.t line 219. # Looks like you failed 2 tests of 1650. t/030-api-coverage.t ... Dubious, test returned 2 (wstat 512, 0x200) Failed 2/1650 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: 1650 Failed: 2) Failed tests: 866, 1575 Non-zero exit status: 2 Files=12, Tests=1904, 66 wallclock secs ( 0.45 usr 0.07 sys + 8.81 cusr 0.62 csys = 9.95 CPU) Result: FAIL Failed 1/12 test programs. 2/1904 subtests failed. Build step 'Execute shell' marked build as failure
1 8
0 0
[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-fedora-29 #236
by ci@centos.org 12 Feb '19

12 Feb '19
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-29/236/…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 236 originally caused by: Started by upstream project "libvirt-perl-build" build number 236 originally caused by: Started by upstream project "libvirt-build" build number 295 originally caused by: 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-29 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-fedora-29/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins5933787411824540051.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 'VIR_DOMAIN_MIGRATE_MAX_SPEED_POSTCOPY' # at t/030-api-coverage.t line 175. # Failed test 'VIR_MIGRATE_PARAM_BANDWIDTH_POSTCOPY' # at t/030-api-coverage.t line 219. # Looks like you failed 2 tests of 1650. t/030-api-coverage.t ... Dubious, test returned 2 (wstat 512, 0x200) Failed 2/1650 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: 1650 Failed: 2) Failed tests: 866, 1575 Non-zero exit status: 2 Files=12, Tests=1904, 56 wallclock secs ( 0.52 usr 0.07 sys + 8.89 cusr 0.55 csys = 10.03 CPU) Result: FAIL Failed 1/12 test programs. 2/1904 subtests failed. Build step 'Execute shell' marked build as failure
1 8
0 0
[Libvirt-ci] Build failed in Jenkins: libvirt-perl-check » libvirt-debian-8 #236
by ci@centos.org 12 Feb '19

12 Feb '19
See <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-debian-8/236/d…> ------------------------------------------ Started by upstream project "libvirt-perl-check" build number 236 originally caused by: Started by upstream project "libvirt-perl-build" build number 236 originally caused by: Started by upstream project "libvirt-build" build number 295 originally caused by: 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-debian-8 (libvirt) in workspace <https://ci.centos.org/job/libvirt-perl-check/systems=libvirt-debian-8/ws/> [libvirt-perl] $ /bin/sh -xe /tmp/jenkins4978077537223621369.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 'VIR_DOMAIN_MIGRATE_MAX_SPEED_POSTCOPY' # at t/030-api-coverage.t line 175. # Failed test 'VIR_MIGRATE_PARAM_BANDWIDTH_POSTCOPY' # at t/030-api-coverage.t line 219. # Looks like you failed 2 tests of 1650. t/030-api-coverage.t ... Dubious, test returned 2 (wstat 512, 0x200) Failed 2/1650 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: 1650 Failed: 2) Failed tests: 866, 1575 Non-zero exit status: 2 Files=12, Tests=1904, 26 wallclock secs ( 0.84 usr 0.14 sys + 13.33 cusr 0.60 csys = 14.91 CPU) Result: FAIL Failed 1/12 test programs. 2/1904 subtests failed. Build step 'Execute shell' marked build as failure
1 8
0 0
  • ← Newer
  • 1
  • ...
  • 692
  • 693
  • 694
  • 695
  • 696
  • 697
  • 698
  • ...
  • 943
  • Older →

HyperKitty Powered by HyperKitty version 1.3.12.