|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [libvirt test] 133728: regressions - FAIL
flight 133728 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/133728/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-libvirt 6 libvirt-build fail REGR. vs. 133672 Tests which did not succeed, but are not blocking: test-amd64-i386-libvirt-xsm 1 build-check(1) blocked n/a test-amd64-i386-libvirt 1 build-check(1) blocked n/a test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 1 build-check(1) blocked n/a test-amd64-i386-libvirt-pair 1 build-check(1) blocked n/a test-armhf-armhf-libvirt 14 saverestore-support-check fail like 133672 test-armhf-armhf-libvirt-raw 13 saverestore-support-check fail like 133672 test-arm64-arm64-libvirt-xsm 13 migrate-support-check fail never pass test-arm64-arm64-libvirt-xsm 14 saverestore-support-check fail never pass test-amd64-amd64-libvirt 13 migrate-support-check fail never pass test-amd64-amd64-libvirt-xsm 13 migrate-support-check fail never pass test-arm64-arm64-libvirt 13 migrate-support-check fail never pass test-arm64-arm64-libvirt 14 saverestore-support-check fail never pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass test-arm64-arm64-libvirt-qcow2 12 migrate-support-check fail never pass test-arm64-arm64-libvirt-qcow2 13 saverestore-support-check fail never pass test-amd64-amd64-libvirt-vhd 12 migrate-support-check fail never pass test-armhf-armhf-libvirt 13 migrate-support-check fail never pass test-armhf-armhf-libvirt-raw 12 migrate-support-check fail never pass version targeted for testing: libvirt 60a0d32e64f578a3bd76b9ed5c6cde4b89f5a3b7 baseline version: libvirt 7a05c739c26decb8ff0eef4f6c75ce3ef729532d Last test of basis 133672 2019-03-09 13:00:19 Z 3 days Testing same since 133728 2019-03-12 04:19:12 Z 1 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Andrea Bolognani <abologna@xxxxxxxxxx> Martin Kletzander <mkletzan@xxxxxxxxxx> Michal Privoznik <mprivozn@xxxxxxxxxx> Shotaro Gotanda <g.sho1500@xxxxxxxxx> jobs: build-amd64-xsm pass build-arm64-xsm pass build-i386-xsm pass build-amd64 pass build-arm64 pass build-armhf pass build-i386 pass build-amd64-libvirt pass build-arm64-libvirt pass build-armhf-libvirt pass build-i386-libvirt fail build-amd64-pvops pass build-arm64-pvops pass build-armhf-pvops pass build-i386-pvops pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm blocked test-amd64-amd64-libvirt-xsm pass test-arm64-arm64-libvirt-xsm pass test-amd64-i386-libvirt-xsm blocked test-amd64-amd64-libvirt pass test-arm64-arm64-libvirt pass test-armhf-armhf-libvirt pass test-amd64-i386-libvirt blocked test-amd64-amd64-libvirt-pair pass test-amd64-i386-libvirt-pair blocked test-arm64-arm64-libvirt-qcow2 pass test-armhf-armhf-libvirt-raw pass test-amd64-amd64-libvirt-vhd pass ------------------------------------------------------------ sg-report-flight on osstest.test-lab.xenproject.org logs: /home/logs/logs images: /home/logs/images Logs, config files, etc. are available at http://logs.test-lab.xenproject.org/osstest/logs Explanation of these reports, and of osstest in general, is at http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master Test harness code can be found at http://xenbits.xen.org/gitweb?p=osstest.git;a=summary Not pushing. ------------------------------------------------------------ commit 60a0d32e64f578a3bd76b9ed5c6cde4b89f5a3b7 Author: Shotaro Gotanda <g.sho1500@xxxxxxxxx> Date: Mon Mar 11 22:19:00 2019 +0900 tests: Run valgrind with absolute path to suppressions file So far we are providing the suppressions file with a relative path to valgrind. This apparently doesn't work on some distros like Ubuntu and its derivates. Providing the absolute path fixes the problem. Signed-off-by: Shotaro Gotanda <g.sho1500@xxxxxxxxx> Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx> commit bc2502f0fc5bc14b7bdb15ecfdeba4f4c3813877 Author: Martin Kletzander <mkletzan@xxxxxxxxxx> Date: Wed Dec 12 13:39:27 2018 +0100 virfilewrapper: Fix indentation Signed-off-by: Martin Kletzander <mkletzan@xxxxxxxxxx> commit 186bb479d0f409dc75175bea48a760838c479a6c Author: Andrea Bolognani <abologna@xxxxxxxxxx> Date: Wed Feb 27 18:41:35 2019 +0100 qemu: Allow creating ppc64 guests with graphics and no USB mouse The existing behavior for ppc64 guests is to always add a USB keyboard and mouse combo if graphics are present; unfortunately, this means any attempt to use a USB tablet will cause both pointing devices to show up in the guest, which in turn will result in poor user experience. We can't just stop adding the USB mouse or start adding a USB tablet instead, because existing applications and users might rely on the current behavior; however, we can avoid adding the USB mouse if a USB tablet is already present, thus allowing users and applications to create guests that contain a single pointing device. https://bugzilla.redhat.com/show_bug.cgi?id=1683681 Signed-off-by: Andrea Bolognani <abologna@xxxxxxxxxx> Reviewed-by: Cole Robinson <crobinso@xxxxxxxxxx> commit 4d7ea75e1e738367c1ff4127a7ff266ec134089a Author: Andrea Bolognani <abologna@xxxxxxxxxx> Date: Wed Feb 27 18:08:29 2019 +0100 tests: Add simple guests with graphics to qemuxml2argv These are similar to the existing simple headless guests, but also include a graphical output and some input devices. Input files were generated by running $ virt-install \$ --name guest --os-variant fedora29 \$ --vcpus 4 --memory 4096 --disk size=5 \$ --graphics vnc \$ --print-xml followed by minor tweaks. Signed-off-by: Andrea Bolognani <abologna@xxxxxxxxxx> Reviewed-by: Cole Robinson <crobinso@xxxxxxxxxx> commit 73bc4f185e314e9738125993b5a72585ea3c42c4 Author: Andrea Bolognani <abologna@xxxxxxxxxx> Date: Wed Mar 6 12:10:05 2019 +0100 docs: Document configuration quirks for virtio devices Some devices (namely virtio-scsi, virtio-gpu, virtio-keyboard, virtio-tablet and virtio-mouse, plus virtio-crypto which is not supported by libvirt) don't follow the same rules as all other virtio devices, which is something that ought to be documented. Signed-off-by: Andrea Bolognani <abologna@xxxxxxxxxx> Reviewed-by: Cole Robinson <crobinso@xxxxxxxxxx> commit ff3f22e0ece293d3c6f6af58d048724d2fcd8039 Author: Andrea Bolognani <abologna@xxxxxxxxxx> Date: Wed Mar 6 12:30:25 2019 +0100 qemu: Improve validation for virtio input devices While the parser and schema have to accept all possible models, virtio-(non-)transitional models are only applicable to type=passthrough and should be otherwise rejected. Signed-off-by: Andrea Bolognani <abologna@xxxxxxxxxx> Reviewed-by: Cole Robinson <crobinso@xxxxxxxxxx> _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |