September 2017 - CI - libvirt List Archives

[Libvirt-ci] Fixed: libvirt/libvirt#518 (master - b065219)
by Travis CI 20 Sep '17

20 Sep '17

Build Update for libvirt/libvirt ------------------------------------- Build: #518 Status: Fixed Duration: 4 hours, 58 minutes, and 26 seconds Commit: b065219 (master) Author: Julio Faracco Message: storage: Add new events for *PoolBuild() and *PoolDelete(). This commit adds new events for two methods and operations: *PoolBuild() and *PoolDelete(). Using the event-test and the commands set below we have the following outputs: $ sudo ./event-test Registering event callbacks myStoragePoolEventCallback EVENT: Storage pool test Defined 0 myStoragePoolEventCallback EVENT: Storage pool test Created 0 myStoragePoolEventCallback EVENT: Storage pool test Started 0 myStoragePoolEventCallback EVENT: Storage pool test Stopped 0 myStoragePoolEventCallback EVENT: Storage pool test Deleted 0 myStoragePoolEventCallback EVENT: Storage pool test Undefined 0 Another terminal: $ sudo virsh pool-define test.xml Pool test defined from test.xml $ sudo virsh pool-build test Pool test built $ sudo virsh pool-start test Pool test started $ sudo virsh pool-destroy test Pool test destroyed $ sudo virsh pool-delete test Pool test deleted $ sudo virsh pool-undefine test Pool test has been undefined This commits can be a solution for RHBZ #1475227. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1475227 Signed-off-by: Julio Faracco <jcfaracco(a)gmail.com> Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/0dde16be73fa...b06521928cca View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/277692413?utm_source=email&utm… -- You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications

1 0

[Libvirt-ci] Fixed: libvirt/libvirt#517 (master - 0dde16b)
by Travis CI 20 Sep '17

20 Sep '17

Build Update for libvirt/libvirt ------------------------------------- Build: #517 Status: Fixed Duration: 5 hours, 2 minutes, and 15 seconds Commit: 0dde16b (master) Author: ZhiPeng Lu Message: qemu: handle reconnect on chardev hotplug The patch passes the reconnect timeout to QEMU by monitor on chardev hotplug. Signed-off-by: ZhiPeng Lu <lu.zhipeng(a)zte.com.cn> Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/c120ce1609de...0dde16be73fa View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/277672234?utm_source=email&utm… -- You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications

1 0

[Libvirt-ci] Fixed: libvirt/libvirt#516 (master - c120ce1)
by Travis CI 20 Sep '17

20 Sep '17

Build Update for libvirt/libvirt ------------------------------------- Build: #516 Status: Fixed Duration: 4 hours, 49 minutes, and 51 seconds Commit: c120ce1 (master) Author: Daniel P. Berrange Message: Link libvirt_util.la with gnutls The util/vircrypto.c file uses gnutls, so we must directly link libvirt_util.la with gnutls to avoid errors on OS which do not resolve symbols against indirectly linked libraries. This fixes a build failure on Ubuntu Trusty CCLD storagevolxml2argvtest /usr/bin/ld: ../src/.libs/libvirt_util.a(libvirt_util_la-vircrypto.o): undefined reference to symbol 'gnutls_strerror@@GNUTLS_1_4' //usr/lib/x86_64-linux-gnu/libgnutls.so.26: error adding symbols: DSO missing from command line Signed-off-by: Daniel P. Berrange <berrange(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/dbd98380b918...c120ce1609de View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/277662797?utm_source=email&utm… -- You can configure 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#515 (master - dbd9838)
by Travis CI 20 Sep '17

20 Sep '17

Build Update for libvirt/libvirt ------------------------------------- Build: #515 Status: Still Failing Duration: 5 hours, 13 minutes, and 40 seconds Commit: dbd9838 (master) Author: Ashish Mittal Message: qemu: Add qemu command line generation for a VxHS block device The VxHS block device will only use the newer formatting options and avoid the legacy URI syntax. An excerpt for a sample QEMU command line is: -drive file.driver=vxhs,file.vdisk-id=eb90327c-8302-4725-9e1b-4e85ed4dc251,\ file.server.type=tcp,file.server.host=192.168.0.1,\ file.server.port=9999,format=raw,if=none,id=drive-virtio-disk0,cache=none \ -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,\ id=virtio-disk0 Update qemuxml2argvtest with a simple test. Signed-off-by: Ashish Mittal <Ashish.Mittal(a)veritas.com> Signed-off-by: John Ferlan <jferlan(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/747116e0b904...dbd98380b918 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/277572138?utm_source=email&utm… -- You can configure 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#514 (master - 747116e)
by Travis CI 20 Sep '17

20 Sep '17

Build Update for libvirt/libvirt ------------------------------------- Build: #514 Status: Still Failing Duration: 5 hours, 13 minutes, and 19 seconds Commit: 747116e (master) Author: Laine Stump Message: util: virPCIGetNetName(): use first netdev name when phys_port_id isn't matched The mlx4 (Mellanox) netdev driver implements the sysfs phys_port_id file for both VFs and PFs, so you can find the VF netdev plugged into the same physical port as any given PF netdev by comparing the contents of phys_port_id of the respective netdevs. That's what libvirt does when attempting to find the PF netdev for a given VF netdev (or vice versa). Most other netdev's drivers don't implement phys_port_id, so the file is visible in sysfs directory listing, but attempts to read it result in ENOTSUPP. In these cases, libvirt is unable to read phys_port_id of either the PF or the VF, so it just returns the first entry in the PF/VF's list of netdevs. But we've found that the i40e driver is in between those two situations - it implements phys_port_id for PF netdevs, but doesn't implement it for VF netdevs. So libvirt would successfully read the phys_port_id of the PF netdev, then try to find a VF netdev with matching phys_port_id, but would fail because phys_port_id is NULL for all VFs. This would result in a message like the following: Could not find network device with phys_port_id '3cfdfe9edc39' under PCI device at /sys/class/net/ens4f1/device/virtfn0 To solve this problem in a way that won't break functionality for anyone else, this patch saves the first netdev name we find for the device, and returns that if we fail to find a netdev with the desired phys_port_id. View the changeset: https://github.com/libvirt/libvirt/compare/8de85386dbcc...747116e0b904 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/277569207?utm_source=email&utm… -- You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications

1 0

[Libvirt-ci] Build failed in Jenkins: virt-manager-master-check » libvirt-centos-7 #818
by ci＠centos.org 20 Sep '17

20 Sep '17

See <https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-centos-…> ------------------------------------------ Started by upstream project "virt-manager-master-check" build number 818 originally caused by: Started by upstream project "virt-manager-master-build" build number 821 originally caused by: Started by upstream project "libvirt-python-master-build" build number 666 originally caused by: Started by upstream project "libvirt-master-build" build number 868 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-centos-7 (libvirt) in workspace <https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-centos-…> [virt-manager-master] $ /bin/sh -xe /tmp/jenkins1947119490082625500.sh + python setup.py test running test ..................................................................................................................................................................................................................................................................................................................................................................................................................................................... ---------------------------------------------------------------------- Ran 437 tests in 368.838s OK /tmp/jenkins1947119490082625500.sh: line 2: 3280 Segmentation fault (core dumped) python setup.py test Build step 'Execute shell' marked build as failure

1 1

[Libvirt-ci] Build failed in Jenkins: virt-manager-master-check » libvirt-centos-7 #816
by ci＠centos.org 20 Sep '17

20 Sep '17

See <https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-centos-…> ------------------------------------------ Started by upstream project "virt-manager-master-check" build number 816 originally caused by: Started by upstream project "virt-manager-master-build" build number 819 originally caused by: Started by upstream project "libvirt-python-master-build" build number 665 originally caused by: Started by upstream project "libvirt-master-build" build number 867 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 Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on libvirt-centos-7 (libvirt) in workspace <https://ci.centos.org/job/virt-manager-master-check/systems=libvirt-centos-…> [virt-manager-master] $ /bin/sh -xe /tmp/jenkins7236479644331643019.sh + python setup.py test running test ..................................................................................................................................................................................................................................................................................................................................................................................................................................................... ---------------------------------------------------------------------- Ran 437 tests in 323.555s OK /tmp/jenkins7236479644331643019.sh: line 2: 16236 Segmentation fault (core dumped) python setup.py test Build step 'Execute shell' marked build as failure

1 1

[Libvirt-ci] Failed: libvirt/libvirt#513 (master - 8de8538)
by Travis CI 20 Sep '17

20 Sep '17

Build Update for libvirt/libvirt ------------------------------------- Build: #513 Status: Failed Duration: 5 hours, 8 minutes, and 48 seconds Commit: 8de8538 (master) Author: Peter Krempa Message: qemu: blockPeek: Enforce buffer filling Documentation states: "'offset' and 'size' represent an area which must lie entirely within the device or file." Enforce the that the buffer lies within fully. View the changeset: https://github.com/libvirt/libvirt/compare/eb3fc2dd2a9e...8de85386dbcc View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/277372858?utm_source=email&utm… -- You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications

1 0

[Libvirt-ci] Failed: libvirt/libvirt#512 (master - eb3fc2d)
by Travis CI 20 Sep '17

20 Sep '17

Build Update for libvirt/libvirt ------------------------------------- Build: #512 Status: Failed Duration: 5 hours, 2 minutes, and 48 seconds Commit: eb3fc2d (master) Author: Andrea Bolognani Message: Revert "travis: Limit git depth to 5 commits" Turns out a build job can be stuck waiting for a macOS worker to become available for a pretty long time: if more than 5 commits have been pushed in the meantime, the clone will be too shallow for the worker to find the commit it's supposed to verify, and the build job will fail. See https://travis-ci.org/libvirt/libvirt/jobs/277244110 for an example of the failure described. This reverts commit 2e975abdc9bbc9e965486e8486cc17a771cdaeb3. Signed-off-by: Andrea Bolognani <abologna(a)redhat.com> Reviewed-by: Daniel P. Berrange <berrange(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/f34fdd5ab606...eb3fc2dd2a9e View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/277359197?utm_source=email&utm… -- You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications

1 0

[Libvirt-ci] Failed: libvirt/libvirt#511 (master - f34fdd5)
by Travis CI 20 Sep '17

20 Sep '17

Build Update for libvirt/libvirt ------------------------------------- Build: #511 Status: Failed Duration: 5 hours, 18 minutes, and 41 seconds Commit: f34fdd5 (master) Author: Andrea Bolognani Message: python: Don't hardcode interpreter path This is particularly useful on operating systems that don't ship Python as part of the base system (eg. FreeBSD) while still working just as well as it did before on Linux. While at it, make it explicit that our scripts are only going to work with Python 2, and remove the usage of unbuffered I/O, which as far as I can tell has no effect on the output files. Signed-off-by: Andrea Bolognani <abologna(a)redhat.com> View the changeset: https://github.com/libvirt/libvirt/compare/8406769642ab...f34fdd5ab606 View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/277329529?utm_source=email&utm… -- You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications

1 0