|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [libvirt test] 113009: regressions - trouble: blocked/broken/fail/pass
flight 113009 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/113009/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-libvirt-xsm 7 xen-boot fail REGR. vs. 112994 Tests which did not succeed, but are not blocking: test-arm64-arm64-libvirt-xsm 1 build-check(1) blocked n/a build-arm64-libvirt 1 build-check(1) blocked n/a test-arm64-arm64-libvirt-qcow2 1 build-check(1) blocked n/a test-arm64-arm64-libvirt 1 build-check(1) blocked n/a build-arm64-pvops 2 hosts-allocate broken like 112994 build-arm64-xsm 2 hosts-allocate broken like 112994 build-arm64 2 hosts-allocate broken like 112994 build-arm64-pvops 3 capture-logs broken like 112994 build-arm64-xsm 3 capture-logs broken like 112994 build-arm64 3 capture-logs broken like 112994 test-armhf-armhf-libvirt-xsm 14 saverestore-support-check fail like 112994 test-armhf-armhf-libvirt 14 saverestore-support-check fail like 112994 test-armhf-armhf-libvirt-raw 13 saverestore-support-check fail like 112994 test-amd64-i386-libvirt 13 migrate-support-check fail never pass test-amd64-i386-libvirt-xsm 13 migrate-support-check fail never pass test-amd64-amd64-libvirt 13 migrate-support-check fail never pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass test-amd64-amd64-libvirt-vhd 12 migrate-support-check fail never pass test-armhf-armhf-libvirt-xsm 13 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 3507dabcd17b6a72289ecb5359ef6c477ab92117 baseline version: libvirt 46ee76daa61108228d5209d71cf1ad09df8195ca Last test of basis 112994 2017-09-01 04:21:44 Z 1 days Testing same since 113009 2017-09-02 04:23:01 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Michal Privoznik <mprivozn@xxxxxxxxxx> Nikolay Shirokovskiy <nshirokovskiy@xxxxxxxxxxxxx> Peter Krempa <pkrempa@xxxxxxxxxx> jobs: build-amd64-xsm pass build-arm64-xsm broken build-armhf-xsm pass build-i386-xsm pass build-amd64 pass build-arm64 broken build-armhf pass build-i386 pass build-amd64-libvirt pass build-arm64-libvirt blocked build-armhf-libvirt pass build-i386-libvirt pass build-amd64-pvops pass build-arm64-pvops broken 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 pass test-amd64-amd64-libvirt-xsm fail test-arm64-arm64-libvirt-xsm blocked test-armhf-armhf-libvirt-xsm pass test-amd64-i386-libvirt-xsm pass test-amd64-amd64-libvirt pass test-arm64-arm64-libvirt blocked test-armhf-armhf-libvirt pass test-amd64-i386-libvirt pass test-amd64-amd64-libvirt-pair pass test-amd64-i386-libvirt-pair pass test-arm64-arm64-libvirt-qcow2 blocked 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 broken-step build-arm64-pvops hosts-allocate broken-step build-arm64-xsm hosts-allocate broken-step build-arm64 hosts-allocate broken-step build-arm64-pvops capture-logs broken-step build-arm64-xsm capture-logs broken-step build-arm64 capture-logs Not pushing. ------------------------------------------------------------ commit 3507dabcd17b6a72289ecb5359ef6c477ab92117 Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Fri Sep 1 14:57:01 2017 +0200 news: Add stuff for 3.7.0 commit 054c6d27214ef90feab3897b052f450492d5ef3f Author: Michal Privoznik <mprivozn@xxxxxxxxxx> Date: Fri Sep 1 10:33:12 2017 +0200 virnetdaemon: Don't deadlock when talking to D-Bus https://bugzilla.redhat.com/show_bug.cgi?id=1487322 In ace45e67abbd I tried to fix a problem that we get the reply to a D-Bus call while we were sleeping. In that case the callback was never set. So I changed the code that the callback is called directly in this case. However, I hadn't realized that since the callback is called out of order it locks the virNetDaemon. Exactly the very same virNetDaemon object that we are dealing with right now and that we have locked already (in virNetDaemonAddShutdownInhibition()) Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx> commit 9820756cd33467815af6d68b2ceef4e567646ec4 Author: Nikolay Shirokovskiy <nshirokovskiy@xxxxxxxxxxxxx> Date: Thu Aug 31 12:01:44 2017 +0300 qemu: handle -1 for pid in qemuDomainGetMachineName We call qemuDomainGetMachineName on domain start. On first start (after daemon start) pid is 0 and virSystemdGetMachineNameByPID don't get called. But after domain shutting down pid became -1 so on next start virSystemdGetMachineNameByPID is called and returned an error. Error is ignored so it is not critical. But at least on my system (systemd-219 with extra patches) systemd-machined is crashed on this request. This behaviour is triggered by eaf2c9f89. Reviewed-by: Daniel P. Berrange <berrange@xxxxxxxxxx> commit f0607f394c5567f3a39b4037bb6fd623363e5aa6 Author: Michal Privoznik <mprivozn@xxxxxxxxxx> Date: Thu Aug 31 11:33:06 2017 +0200 qemu: Forbid rx/tx_queue_size change explicitly https://bugzilla.redhat.com/show_bug.cgi?id=1484230 When updating a virtio enabled vNIC and trying to change either of rx_queue_size or tx_queue_size success is reported although no operation is actually performed. Moreover, there's no way how to change these on the fly. This is due to way we check for changes: explicitly for each struct member. Therefore it's easy to miss one. Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx> _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |