Build Update for libvirt/libvirt
-------------------------------------
Build: #206
Status: Fixed
Duration: 23 minutes and 33 seconds
Commit: 6451b55 (master)
Author: Michal Privoznik
Message: qemuDomainGetPreservedMounts: Fix suffixes for corner cases
https://bugzilla.redhat.com/show_bug.cgi?id=1431112
Imagine a FS mounted on /dev/blah/blah2. Our process of creating
suffix for temporary location where all the mounted filesystems
are moved is very simplistic. We want:
/var/run/libvirt/qemu/$domName.$suffix\
were $suffix is just the mount point path stripped of the "/dev/"
prefix. For instance:
/var/run/libvirt/qemu/fedora.mqueue for /dev/mqueue
/var/run/libvirt/qemu/fedora.pts for /dev/pts
and so on. Now if we plug /dev/blah/blah2 into the example we see
some misbehaviour:
/var/run/libvirt/qemu/fedora.blah/blah2
Well, misbehaviour if /dev/blah/blah2 is a file, because in that
case we call virFileTouch() instead of virFileMakePath().
The solution is to replace all the slashes in the suffix with say
dots. That way we don't have to care about nested directories.
IOW, the result we want for given example is:
/var/run/libvirt/qemu/fedora.blah.blah2
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/cc9f0521cda6...6451b55ec3d8
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/243652850?utm_source=email&utm…
--
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
Build Update for libvirt/libvirt
-------------------------------------
Build: #205
Status: Broken
Duration: 17 minutes and 7 seconds
Commit: cc9f052 (master)
Author: Martin Kletzander
Message: Report more correct information for cache control
On some platforms the number of bits in the cbm_mask might not be
divisible by 4 (and not even by 2), so we need to properly count the
bits. Similar file, min_cbm_bits, is properly parsed and used, but if
the number is greater than one, we lose the information about
granularity when reporting the data in capabilities. For that matter
always report granularity, but if it is not the same as the minimum,
add that information in there as well.
Signed-off-by: Martin Kletzander <mkletzan(a)redhat.com>
View the changeset: https://github.com/libvirt/libvirt/compare/ba326c869948...cc9f0521cda6
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/243628176?utm_source=email&utm…
--
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
Build Update for libvirt/libvirt
-------------------------------------
Build: #204
Status: Passed
Duration: 24 minutes and 27 seconds
Commit: ba326c8 (master)
Author: Serge Hallyn
Message: apparmor, libvirt-qemu: Allow access to certificates used by libvirt-vnc
When setting up VncTLS according to the official Libvirt documentation,
only one certificate for libvirt/libvirt-vnc is used. The document
indicates to use the following directories :
/etc/pki/CA
/etc/pki/libvirt
/etc/pki/libvirt/private
in order to manage the certificates used by libvirt-vnc.
Bug-Ubuntu: https://bugs.launchpad.net/bugs/901272
Signed-off-by: Christian Ehrhardt <christian.ehrhardt(a)canonical.com>
Signed-off-by: Stefan Bader <stefan.bader(a)canonical.com>
View the changeset: https://github.com/libvirt/libvirt/compare/307a205e25ad...ba326c869948
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/243584971?utm_source=email&utm…
--
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
Build Update for libvirt/libvirt
-------------------------------------
Build: #202
Status: Errored
Duration: 50 minutes and 21 seconds
Commit: f1acc41 (master)
Author: Daniel P. Berrange
Message: Temporarily disable format truncation warnings
GCC 7.1 introduces a new -Wformat-truncation warning
flag that reports if it thinks the maximum possible
size of the formatted output will exceed the provided
fixed buffer. This is enabled automatically by the
-Wformat warning flag. There are quite a few places
hit by this in libvirt which need rewriting. This is
non-trivial work in some places, so temporarily
disable the new warning until those fixes can be
implemented.
Signed-off-by: Daniel P. Berrange <berrange(a)redhat.com>
View the changeset: https://github.com/libvirt/libvirt/compare/1ba693994a0e...f1acc4130c4d
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/243329412?utm_source=email&utm…
--
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
Build Update for libvirt/libvirt
-------------------------------------
Build: #201
Status: Passed
Duration: 23 minutes and 4 seconds
Commit: 1ba6939 (master)
Author: Daniel P. Berrange
Message: Disable the -Wduplicated-branches warning
Depending on the platform/architecture, a number of conditionals
in libvirt code expand the same on both branches. This is expected
behaviour and harmless, so disable the warning to avoid creating
unexpected build failures
Two examples, mingw32:
../../src/util/vircommand.c: In function 'virCommandWait':
../../src/util/vircommand.c:2562:51: error: this condition has identical branches [-Werror=duplicated-branches]
*exitstatus = cmd->rawStatus ? status : WEXITSTATUS(status);
^
and gcc7.1
In file included from util/virobject.c:28:0:
util/virobject.c: In function 'virClassNew':
util/viratomic.h:176:46: error: this condition has identical branches [-Werror=duplicated-branches]
(void)(0 ? *(atomic) ^ *(atomic) : 0); \
^
util/virobject.c:144:20: note: in expansion of macro 'virAtomicIntInc'
klass->magic = virAtomicIntInc(&magicCounter);
^~~~~~~~~~~~~~~
Signed-off-by: Daniel P. Berrange <berrange(a)redhat.com>
View the changeset: https://github.com/libvirt/libvirt/compare/f0a3fe1b0a29...1ba693994a0e
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/243244113?utm_source=email&utm…
--
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
Build Update for libvirt/libvirt
-------------------------------------
Build: #200
Status: Errored
Duration: 59 minutes and 40 seconds
Commit: f0a3fe1 (master)
Author: Jiri Denemark
Message: qemu: Use qemuDomainCheckABIStability where needed
Most places which want to check ABI stability for an active domain need
to call this API rather than the original
qemuDomainDefCheckABIStability. The only exception is in snapshots where
we need to decide what to do depending on the saved image data.
https://bugzilla.redhat.com/show_bug.cgi?id=1460952
Signed-off-by: Jiri Denemark <jdenemar(a)redhat.com>
Reviewed-by: Pavel Hrdina <phrdina(a)redhat.com>
View the changeset: https://github.com/libvirt/libvirt/compare/1e8d6c6ef07a...f0a3fe1b0a29
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/242875006?utm_source=email&utm…
--
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
Build Update for libvirt/libvirt
-------------------------------------
Build: #196
Status: Errored
Duration: 27 minutes and 16 seconds
Commit: bb12db1 (master)
Author: Erik Skultety
Message: qemu: monitor: Fix a memory leak in qemuMonitorJSONAttachCharDevCommand
With the current logic, we only free @tlsalias as part of the error
label and would have to free it explicitly earlier in the code. Convert
the error label to cleanup, so that we have only one sink, where we
handle all frees. Since JSON object append operation consumes pointers,
make sure @backend is cleared before we hit the cleanup label.
Signed-off-by: Erik Skultety <eskultet(a)redhat.com>
Reviewed-by: Pavel Hrdina <phrdina(a)redhat.com>
View the changeset: https://github.com/libvirt/libvirt/compare/992bf863fccf...bb12db16b410
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/242746313?utm_source=email&utm…
--
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
