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 -----
  • 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

November 2019

  • 2 participants
  • 80 discussions
[Libvirt-ci] Build failed in Jenkins: libosinfo-build » libvirt-centos-7 #271
by ci@centos.org 27 Nov '19

27 Nov '19
See <https://ci.centos.org/job/libosinfo-build/systems=libvirt-centos-7/271/disp…> Changes: [fidencio] device-driver: Add "priority" attribute [fidencio] os: Add "get_device_drivers_prioritized" ------------------------------------------ Started by upstream project "libosinfo-build" build number 271 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 Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on libvirt-centos-7 (libvirt) in workspace <https://ci.centos.org/job/libosinfo-build/systems=libvirt-centos-7/ws/> No credentials specified Cloning the remote Git repository Cloning repository https://gitlab.com/libosinfo/libosinfo.git > git init <https://ci.centos.org/job/libosinfo-build/systems=libvirt-centos-7/ws/> # timeout=10 Fetching upstream changes from https://gitlab.com/libosinfo/libosinfo.git > git --version # timeout=10 > git fetch --tags --progress https://gitlab.com/libosinfo/libosinfo.git +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url https://gitlab.com/libosinfo/libosinfo.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://gitlab.com/libosinfo/libosinfo.git # timeout=10 Fetching upstream changes from https://gitlab.com/libosinfo/libosinfo.git > git fetch --tags --progress https://gitlab.com/libosinfo/libosinfo.git +refs/heads/*:refs/remotes/origin/* Checking out Revision afffabae21a99efa42047cd65c5cdfa05babc259 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f afffabae21a99efa42047cd65c5cdfa05babc259 Commit message: "os: Add "get_device_drivers_prioritized"" > git rev-list --no-walk 5011123a6159e7293dc8a64159268c9abf96939f # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 [libosinfo] $ /bin/sh -xe /tmp/jenkins8854951521072142696.sh + rm -rf build + mkdir build + cd build + meson .. . --prefix=/home/jenkins/build/libvirt /tmp/jenkins8854951521072142696.sh: line 6: meson: command not found Build step 'Execute shell' marked build as failure
1 1
0 0
[Libvirt-ci] Still Failing: libvirt/libvirt#2892 (master - 83254ea)
by Travis CI 27 Nov '19

27 Nov '19
Build Update for libvirt/libvirt ------------------------------------- Build: #2892 Status: Still Failing Duration: 38 mins and 11 secs Commit: 83254ea (master) Author: Michal Privoznik Message: news: Update for 5.10.0 release Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> Reviewed-by: Ján Tomko <jtomko(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/d310b0869753...83254ea750b4 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/617797081?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#2891 (master - d310b08)
by Travis CI 27 Nov '19

27 Nov '19
Build Update for libvirt/libvirt ------------------------------------- Build: #2891 Status: Still Failing Duration: 40 mins and 1 sec Commit: d310b08 (master) Author: Peter Krempa Message: qemu: blockjob: Finish handling job with broken data Now that we have a separate job type which will not trigger normal code paths for terminating job we can remove the ad-hoc handling. This possibly fixes the issue of a broken job inheriting the disk and then finishing in which case we'd not detach the backing chain. Signed-off-by: Peter Krempa <pkrempa(a)redhat.com> Reviewed-by: Cole Robinson <crobinso(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/27660f7990f2...d310b0869753 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/617770658?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#2890 (master - 27660f7)
by Travis CI 27 Nov '19

27 Nov '19
Build Update for libvirt/libvirt ------------------------------------- Build: #2890 Status: Still Failing Duration: 38 mins and 40 secs Commit: 27660f7 (master) Author: Daniel P. Berrangé Message: util: whitelist Oracle ACFS as a shared filesystem The magic number is taken from the coreutils stat.c file since there is no constant for it in normal system headers. Reviewed-by: Daniel Henrique Barboza <danielhb413(a)gmail.com> Signed-off-by: Daniel P. Berrangé <berrange(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/a10eb613404f...27660f7990f2 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/617749660?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#2889 (master - a10eb61)
by Travis CI 27 Nov '19

27 Nov '19
Build Update for libvirt/libvirt ------------------------------------- Build: #2889 Status: Still Failing Duration: 39 mins and 13 secs Commit: a10eb61 (master) Author: Peter Krempa Message: Revert "qemu: Don't repeat virDomainObjEndAPI in qemuDomainBlockPull" This reverts commit 421c9550f5446729b513ee50f5c44e6f6969b5a2 qemuDomainBlockPullCommon calls virDomainObjEndAPI internally so the original commit made us shed two references of @vm instead of one getting us into a premature free of @vm. This is not a straight revert as qemuDomainBlockPull was modified meanwhile. I've also added a warning comment that @vm is consumed. https://bugzilla.redhat.com/show_bug.cgi?id=1777230 Signed-off-by: Peter Krempa <pkrempa(a)redhat.com> Reviewed-by: Ján Tomko <jtomko(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/c8579871a980...a10eb613404f View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/617724609?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] Errored: libvirt/libvirt#2888 (v5.10.0-rc1 - c857987)
by Travis CI 26 Nov '19

26 Nov '19
Build Update for libvirt/libvirt ------------------------------------- Build: #2888 Status: Errored Duration: 24 mins and 53 secs Commit: c857987 (v5.10.0-rc1) Author: Michal Privoznik Message: all: don't wait for driver lock during startup There are two daemons that wait for acquiring their pid files: virtnetworkd and virtstoraged. This is undesirable as the idea is to quit early if unable to acquire the pid file. Fixes: v5.6.0-rc1~207. Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> Reviewed-by: Ján Tomko <jtomko(a)redhat.com> Reviewed-by: Daniel P. Berrangé <berrange(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/v5.10.0-rc1 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/617430558?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#2887 (master - c857987)
by Travis CI 26 Nov '19

26 Nov '19
Build Update for libvirt/libvirt ------------------------------------- Build: #2887 Status: Still Failing Duration: 42 mins and 33 secs Commit: c857987 (master) Author: Michal Privoznik Message: all: don't wait for driver lock during startup There are two daemons that wait for acquiring their pid files: virtnetworkd and virtstoraged. This is undesirable as the idea is to quit early if unable to acquire the pid file. Fixes: v5.6.0-rc1~207. Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> Reviewed-by: Ján Tomko <jtomko(a)redhat.com> Reviewed-by: Daniel P. Berrangé <berrange(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/3b9359cd44b5...c8579871a980 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/617254145?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#2886 (master - 3b9359c)
by Travis CI 26 Nov '19

26 Nov '19
Build Update for libvirt/libvirt ------------------------------------- Build: #2886 Status: Still Failing Duration: 37 mins and 50 secs Commit: 3b9359c (master) Author: Peter Krempa Message: check-symfile: Use pythonesque string formatting instead of perl Commit d30a1ad0443 translated the symbol file checker from perl to python by doing a literal translation in most cases. Unfortunately one string formatting operation was not really translated into python leaving users with non-helpful error: 'Symbol $1 is listed twice' Signed-off-by: Peter Krempa <pkrempa(a)redhat.com> Reviewed-by: Erik Skultety <eskultet(a)redhat.com> Reviewed-by: Michal Privoznik <mprivozn(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/9d6920bd7de3...3b9359cd44b5 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/617108221?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#2885 (master - 9d6920b)
by Travis CI 25 Nov '19

25 Nov '19
Build Update for libvirt/libvirt ------------------------------------- Build: #2885 Status: Still Failing Duration: 41 mins and 18 secs Commit: 9d6920b (master) Author: Laine Stump Message: net/qemu: move vlan/bandwidth validation out of network driver In the past the network driver was (mistakenly) being called for all interfaces, not just those of type='network', and so it had a chance to validate all interface configs after the actual type of the interface was known. But since the network driver has been more completely/properly separated from qemu, the network driver isn't called during the startup of any interfaces except those with type='network', so this validation no longer takes place for, e.g. <interface type='bridge'> (or direct, etc). This in turn meant that a config could erroneously specify a vlan tag, or bandwidth settings, for a type of interface that didn't support it, and the domain would start without complaint, just silently ignoring those settings. This patch moves those validation checks out of the network driver, and into virDomainActualNetDefValidate() so they will be done for all interfaces, not just type='network'. https://bugzilla.redhat.com/1741121 Signed-off-by: Laine Stump <laine(a)redhat.com> Reviewed-by: Cole Robinson <crobinso(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/9b1d53d4170c...9d6920bd7de3 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/616877000?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#2884 (master - 9b1d53d)
by Travis CI 25 Nov '19

25 Nov '19
Build Update for libvirt/libvirt ------------------------------------- Build: #2884 Status: Still Failing Duration: 43 mins and 1 sec Commit: 9b1d53d (master) Author: Michal Privoznik Message: qemu_capabilities: Use proper free function for caps->cpuModels The cpuModels member of _virQEMUCapsAccel struct is not a virObject but regular struct with a free function defined: qemuMonitorCPUDefsFree(). Use that when clearing parent structure instead of virObjectUnref() to avoid a memleak: ==212322== 57,275 (48 direct, 57,227 indirect) bytes in 3 blocks are definitely lost in loss record 623 of 627 ==212322== at 0x4838B86: calloc (vg_replace_malloc.c:762) ==212322== by 0x554A158: g_malloc0 (in /usr/lib64/libglib-2.0.so.0.6000.6) ==212322== by 0x17B14BF5: qemuMonitorCPUDefsNew (qemu_monitor.c:3587) ==212322== by 0x17B27BA7: qemuMonitorJSONGetCPUDefinitions (qemu_monitor_json.c:5616) ==212322== by 0x17B14B0B: qemuMonitorGetCPUDefinitions (qemu_monitor.c:3559) ==212322== by 0x17A6AFBB: virQEMUCapsFetchCPUDefinitions (qemu_capabilities.c:2571) ==212322== by 0x17A6B2CC: virQEMUCapsProbeQMPCPUDefinitions (qemu_capabilities.c:2629) ==212322== by 0x17A70C00: virQEMUCapsInitQMPMonitorTCG (qemu_capabilities.c:4769) ==212322== by 0x17A70DDF: virQEMUCapsInitQMPSingle (qemu_capabilities.c:4820) ==212322== by 0x17A70E99: virQEMUCapsInitQMP (qemu_capabilities.c:4848) ==212322== by 0x17A71044: virQEMUCapsNewForBinaryInternal (qemu_capabilities.c:4891) ==212322== by 0x17A7119C: virQEMUCapsNewData (qemu_capabilities.c:4923) Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> Reviewed-by: Jiri Denemark <jdenemar(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/24d820229485...9b1d53d4170c View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/616768700?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
  • Older →

HyperKitty Powered by HyperKitty version 1.3.12.