- CI - libvirt List Archives

[Libvirt-ci] Errored: libvirt/libvirt#2888 (v5.10.0-rc1 - c857987)
by Travis CI 27 Nov '19

27 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

[Libvirt-ci] Still Failing: libvirt/libvirt#2887 (master - c857987)
by Travis CI 27 Nov '19

27 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

[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

[Libvirt-ci] Still Failing: libvirt/libvirt#2885 (master - 9d6920b)
by Travis CI 26 Nov '19

26 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

[Libvirt-ci] Still Failing: libvirt/libvirt#2884 (master - 9b1d53d)
by Travis CI 26 Nov '19

26 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

[Libvirt-ci] Still Failing: libvirt/libvirt#2883 (master - 24d8202)
by Travis CI 26 Nov '19

26 Nov '19

Build Update for libvirt/libvirt ------------------------------------- Build: #2883 Status: Still Failing Duration: 44 mins and 17 secs Commit: 24d8202 (master) Author: Jiri Denemark Message: qemu: Use host-model CPU on s390 by default On s390 machines host-passthrough and host-model CPUs result in the same guest ABI (with QEMU new enough to be able to tell us what "host" CPU is expanded to, which was implemented around 2.9.0). So instead of using host-passthrough CPU when there's no CPU specified in a domain XML we can safely use host-model and benefit from CPU compatibility checks during migration, snapshot restore and similar operations. Signed-off-by: Jiri Denemark <jdenemar(a)redhat.com> Reviewed-by: Ján Tomko <jtomko(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/d3f2a8bd472a...24d820229485 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/616717431?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

[Libvirt-ci] Failed: libvirt/libvirt#2882 (master - d3f2a8b)
by Travis CI 26 Nov '19

26 Nov '19

Build Update for libvirt/libvirt ------------------------------------- Build: #2882 Status: Failed Duration: 36 mins and 50 secs Commit: d3f2a8b (master) Author: Pavel Mores Message: qemu: added tests of the new default video type selection algorithm The test case for x86_64 and neither cirrus nor vga capability is of the xml2argv type because it actually fails to parse the XML at all [*] which is something that xml2xml tests don't seem to handle. xml2argv test fails to produce a qemu argv for this case which xml2argv tests can handle. [*] This is a consequence of the decision not to have a fallback if the obvious choices (cirrus and vga) aren't viable due to missing QEMU caps. Reviewed-by: Cole Robinson <crobinso(a)redhat.com> Signed-off-by: Pavel Mores <pmores(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/68aa7f38511e...d3f2a8bd472a View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/616695355?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

[Libvirt-ci] Errored: libvirt/libvirt#2881 (master - 68aa7f3)
by Travis CI 25 Nov '19

25 Nov '19

Build Update for libvirt/libvirt ------------------------------------- Build: #2881 Status: Errored Duration: 37 mins and 23 secs Commit: 68aa7f3 (master) Author: Daniel P. Berrangé Message: travis: add fedora-31 & fedora-rawhide to the build images The CentOS7 distro is quite old and the Ubuntu 18.04 distro is already a year & half old. Adding a Fedora 31 image gives us coverage of the newest stable distro release, and fedora-rawhide gives us the cutting edge. Reviewed-by: Fabiano Fidêncio <fidencio(a)redhat.com> Signed-off-by: Daniel P. Berrangé <berrange(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/36a01c2a4720...68aa7f38511e View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/616608564?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

[Libvirt-ci] Errored: libvirt/libvirt#2880 (master - 36a01c2)
by Travis CI 25 Nov '19

25 Nov '19

Build Update for libvirt/libvirt ------------------------------------- Build: #2880 Status: Errored Duration: 9 mins and 54 secs Commit: 36a01c2 (master) Author: Erik Skultety Message: Revert "network: Check for QOS before blindly using it" This reverts commit f4db846c32c0a1e99a0f62b340273e48f8a98ed3. This patch results in the following error when trying to start essentially any VM with default network: unsupported configuration: QOS must be defined for network 'default' Coverity didn't see that the bandwidth == NULL it complained about in virNetDevBandwidthPlug was already checked properly in networkCheckBandwidth, thus causing networkPlugBandwidth to return 0 and finish before a call to virNetDevBandwidthPlug would have been even made. Signed-off-by: Erik Skultety <eskultet(a)redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413(a)gmail.com> Reviewed-by: Jiri Denemark <jdenemar(a)redhat.com> Reviewed-by: Michal Privoznik <mprivozn(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/bc7e72914a07...36a01c2a4720 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/616570494?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

[Libvirt-ci] Still Failing: libvirt/libvirt#2879 (master - bc7e729)
by Travis CI 23 Nov '19

23 Nov '19

Build Update for libvirt/libvirt ------------------------------------- Build: #2879 Status: Still Failing Duration: 21 mins and 22 secs Commit: bc7e729 (master) Author: Daniel P. Berrangé Message: util: consolidate on one free callback for hash data This previous commit introduced a simpler free callback for hash data with only 1 arg, the value to free: commit 49288fac965f0ee23db45d83ae4ef3a9a71dafd0 Author: Peter Krempa <pkrempa(a)redhat.com> Date: Wed Oct 9 15:26:37 2019 +0200 util: hash: Add possibility to use simpler data free function in virHash It missed two functions in the hash table code which need to call the alternate data free function, virHashRemoveEntry and virHashRemoveSet. After the previous patch though, there is no code that makes functional use of the 2nd key arg in the data free function. There is merely one log message that can be dropped. We can thus purge the current virHashDataFree callback entirely, and rename virHashDataFreeSimple to replace it. Reviewed-by: Michal Privoznik <mprivozn(a)redhat.com> Signed-off-by: Daniel P. Berrangé <berrange(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/c6a9e54ce325...bc7e72914a07 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/615577662?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