Build Update for libvirt/libvirt
-------------------------------------
Build: #812
Status: Errored
Duration: 24 minutes and 2 seconds
Commit: 65dace5 (master)
Author: Bjoern Walk
Message: tests: virhostcputest: testcase for S390 system
Let's add a testcase for a S390 system running kernel version 4.14 on
LPAR.
Reviewed-by: Marc Hartmayer <mhartmay(a)linux.vnet.ibm.com>
Reviewed-by: Boris Fiuczynski <fiuczy(a)linux.vnet.ibm.com>
Signed-off-by: Bjoern Walk <bwalk(a)linux.vnet.ibm.com>
View the changeset: https://github.com/libvirt/libvirt/compare/be1bb6c95b31...65dace5a96d7
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/327450301?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: #811
Status: Errored
Duration: 41 minutes and 16 seconds
Commit: be1bb6c (master)
Author: John Ferlan
Message: storage: Complete implementation volume by hash object
Alter the volume logic to use the hash tables instead of forward
linked lists. There are three hash tables to allow for fast lookup
by name, target.path, and key.
Modify the virStoragePoolObjAddVol to place the object in all 3
tables if possible using self locking RWLock on the volumes object.
Conversely when removing the volume, it's a removal of the object
from the various hash tables.
Implement functions to handle remote ForEach and Search Volume
type helpers. These are used by the disk backend in order to
facilitate adding a primary, extended, or logical partition.
Implement the various VolDefFindBy* helpers as simple (and fast)
hash lookups. The NumOfVolumes, GetNames, and ListExport helpers
are all implemented using standard for each hash table calls.
View the changeset: https://github.com/libvirt/libvirt/compare/b427cf4831d0...be1bb6c95b31
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/327439065?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: #810
Status: Errored
Duration: 24 minutes and 4 seconds
Commit: b427cf4 (master)
Author: Jiri Denemark
Message: cpu_x86: Copy CPU signature from ancestor
When specifying a new CPU model in cpu_map.xml as an extension to an
existing model, we forgot to copy the signature (family + model) from
the original CPU model.
We don't use this way of specifying CPU models, but it's still supported
and it becomes useful when someone wants to quickly hack up a CPU model
for testing or when creating additional variants of existing models to
help with fixing some spectral issues.
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/335ea94e311f...b427cf4831d0
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/327199482?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: #808
Status: Errored
Duration: 25 minutes and 57 seconds
Commit: 5924977 (master)
Author: Jamie Strandboge
Message: apparmor, virt-aa-helper: Allow access to /sys/bus/usb/devices
Required to generate correct profiles when using usb passthrough.
Bug-Ubuntu: https://bugs.launchpad.net/bugs/565691
Signed-off-by: Stefan Bader <stefan.bader(a)canonical.com>
Signed-off-by: Christian Ehrhardt <christian.ehrhardt(a)canonical.com>
Acked-by: Jamie Strandboge <jamie(a)ubuntu.com>
Acked-by: Intrigeri <intrigeri(a)boum.org>
View the changeset: https://github.com/libvirt/libvirt/compare/058b7fd0fe7a...592497787056
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/326732583?utm_source=email&utm…
--
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
