|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [libvirt test] 78066: regressions - FAIL
flight 78066 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/78066/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-libvirt-raw 6 xen-boot fail REGR. vs. 77871 Regressions which are regarded as allowable (not blocking): test-amd64-amd64-libvirt-vhd 9 debian-di-install fail like 77871 Tests which did not succeed, but are not blocking: test-armhf-armhf-libvirt-xsm 12 migrate-support-check fail never pass test-armhf-armhf-libvirt-xsm 14 guest-saverestore fail never pass test-armhf-armhf-libvirt-qcow2 11 migrate-support-check fail never pass test-armhf-armhf-libvirt-qcow2 13 guest-saverestore fail never pass test-amd64-i386-libvirt-xsm 12 migrate-support-check fail never pass test-armhf-armhf-libvirt 14 guest-saverestore fail never pass test-armhf-armhf-libvirt 12 migrate-support-check fail never pass test-amd64-amd64-libvirt 12 migrate-support-check fail never pass test-amd64-i386-libvirt 12 migrate-support-check fail never pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass test-amd64-amd64-libvirt-xsm 12 migrate-support-check fail never pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass version targeted for testing: libvirt f99f79e380326cd1259721e134c074bf271f4269 baseline version: libvirt 545e5571f9bafc61c65b563ca69907f8cc935f72 Last test of basis 77871 2016-01-12 01:15:10 Z 2 days Failing since 77934 2016-01-12 23:13:18 Z 1 days 3 attempts Testing same since 78066 2016-01-14 08:03:25 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Andrea Bolognani <abologna@xxxxxxxxxx> Ben Gray <ben.r.gray@xxxxxxxxx> Cole Robinson <crobinso@xxxxxxxxxx> Dmitry Andreev <dandreev@xxxxxxxxxxxxx> Guido Günther <agx@xxxxxxxxxxx> Jim Fehlig <jfehlig@xxxxxxxx> Martin Kletzander <mkletzan@xxxxxxxxxx> Michal Privoznik <mprivozn@xxxxxxxxxx> Roman Bogorodskiy <bogorodskiy@xxxxxxxxx> jobs: build-amd64-xsm pass build-armhf-xsm pass build-i386-xsm pass build-amd64 pass build-armhf pass build-i386 pass build-amd64-libvirt pass build-armhf-libvirt pass build-i386-libvirt pass build-amd64-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 pass test-amd64-amd64-libvirt-xsm pass test-armhf-armhf-libvirt-xsm fail test-amd64-i386-libvirt-xsm pass test-amd64-amd64-libvirt pass test-armhf-armhf-libvirt fail test-amd64-i386-libvirt pass test-amd64-amd64-libvirt-pair pass test-amd64-i386-libvirt-pair pass test-armhf-armhf-libvirt-qcow2 fail test-armhf-armhf-libvirt-raw fail test-amd64-amd64-libvirt-vhd fail ------------------------------------------------------------ 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 f99f79e380326cd1259721e134c074bf271f4269 Author: Michal Privoznik <mprivozn@xxxxxxxxxx> Date: Wed Jan 13 16:10:15 2016 +0100 wireshark: Drop DESTDIR from install path In 50078cfbcbf3c8 I've tried to fix distcheck but accidentally broke rpm build. The problem is that rpm build not only sets DESTDIR but also passes plugindir path. This results in double DESTDIR being in the plugin path, Drop one. Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx> commit e8f771176e8ccc69a37882cc350ab34fcf869d2d Author: Guido Günther <agx@xxxxxxxxxxx> Date: Wed Jan 13 08:47:26 2016 +0100 virsh: Update description of lxc-enter-namespace Mention that we run a command in that namespace commit e20dd2a4fd958900ea76d1e8e1890d2d93ebdcd8 Author: Cole Robinson <crobinso@xxxxxxxxxx> Date: Tue Jan 12 15:56:42 2016 -0500 build: fix distdir with wireshark disabled Even though the Makefile has WITH_WIRESHARK guards, the _SOURCES variables are still processed when adding bits to the dist archive. plugin.c is a generated file that is only built when wireshark is enabled and it shouldn't be distributed, so use 'nodist' commit e988ba94aa5e2db450bd11585101cd93795eb116 Author: Michal Privoznik <mprivozn@xxxxxxxxxx> Date: Wed Jan 13 11:17:24 2016 +0100 qemuProcessCleanupChardevDevice: Don't unlink NULL paths So, you try to start a domain, but before we even get to the part where chardev part of qemu command line is generated (and possibly missing path to unix sockets is made up) an error occurs which results in calling qemuProcessStop. This will then try to clean up the mess and possibly ends up calling unlink(NULL). ==8085== Thread 3: ==8085== Syscall param unlink(pathname) points to unaddressable byte(s) ==8085== at 0xA85EA57: unlink (in /lib64/libc-2.21.so) ==8085== by 0x213D3C24: qemuProcessCleanupChardevDevice (qemu_process.c:2866) ==8085== by 0x558D6B1: virDomainChrDefForeach (domain_conf.c:22924) ==8085== by 0x213DA9AE: qemuProcessStop (qemu_process.c:5326) ==8085== by 0x213DA2F2: qemuProcessStart (qemu_process.c:5190) ==8085== by 0x2142957F: qemuDomainObjStart (qemu_driver.c:7396) ==8085== by 0x214297DB: qemuDomainCreateWithFlags (qemu_driver.c:7450) ==8085== by 0x21429842: qemuDomainCreate (qemu_driver.c:7468) ==8085== by 0x5611B95: virDomainCreate (libvirt-domain.c:6753) ==8085== by 0x125D9A: remoteDispatchDomainCreate (remote_dispatch.h:3613) ==8085== by 0x125CB7: remoteDispatchDomainCreateHelper (remote_dispatch.h:3589) ==8085== by 0x568BF41: virNetServerProgramDispatchCall (virnetserverprogram.c:437) ==8085== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==8085== Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx> commit 71daae9671e287bb1947c49b0b07733692bcb60f Author: Jim Fehlig <jfehlig@xxxxxxxx> Date: Tue Jan 12 11:34:06 2016 -0700 xenconfig: check return value of regcomp Commit ec63000a missed checking the return value of regcomp(), which coverity promptly identified. commit 50078cfbcbf3c802e9c93f219cc42e5e3818e537 Author: Michal Privoznik <mprivozn@xxxxxxxxxx> Date: Tue Jan 12 17:20:08 2016 +0100 wireshark: Install into DESTDIR Like everything we install, it should be prefixed with DESTDIR. Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx> commit 6564de5e952959080631c1b80173fe8679cd072c Author: Jim Fehlig <jfehlig@xxxxxxxx> Date: Mon Jan 11 15:17:53 2016 -0700 Xen: use correct domctl version in domaininfolist union Commmit fd2e3c4c used the domctl version 8 structure for version 9 in the xen_getdomaininfolist union, resulting in insufficient buffer size (and subsequent memory corruption) for the GETDOMAININFOLIST ioctl. Signed-off-by: Jim Fehlig <jfehlig@xxxxxxxx> commit ebfd6f45c385bb04623479bab7a77beb3ffe167b Author: Cole Robinson <crobinso@xxxxxxxxxx> Date: Tue Jan 12 10:55:08 2016 -0500 testutils: Fix coverity warning with REGENERATE_OUTPUT - Don't double check for expectName - actual is always non-NULL by this point, so don't check it either commit 3445acdbaa284c6d32600e03be58f513a8a6519a Author: Cole Robinson <crobinso@xxxxxxxxxx> Date: Sun Jan 10 15:35:36 2016 -0500 build: Kill tools/wireshark Makefiles Just handle it all in tools/Makefile.am. I verified the generated output looks similar to the pre patch output, but I didn't test it. commit 8c67ab6684e984bcf7f4de3e6eee9d19b219a369 Author: Michal Privoznik <mprivozn@xxxxxxxxxx> Date: Tue Jan 12 16:22:24 2016 +0100 Expand $(wildcard) correctly So after da176bf6b756 and friend we have switched to $(wildcard some/path/*.xml) instead of enumerating the files explicitly. This is nice, however it makes distcheck build from VPATH fail. The reason is that it's is not obvious to what does the wildcard refer to: srcdir or builddir? Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx> commit 981c01d419782af2e38f71f42a21091aeb0754b7 Author: Dmitry Andreev <dandreev@xxxxxxxxxxxxx> Date: Fri Jan 8 13:45:07 2016 +0300 qemu: add support of optional 'autodeflate' attribute Autodeflate can be enabled/disabled for memballon device of model 'virtio'. xml: <devices> <memballoon model='virtio' autodeflate='on'/> </devices> qemu: qemu -device virtio-balloon-pci,...,deflate-on-oom=on Autodeflate cannot be enabled/disabled for running domain. commit 3522a311ea4c9f9b2bccecfced7434f2bd6fabc4 Author: Dmitry Andreev <dandreev@xxxxxxxxxxxxx> Date: Fri Jan 8 13:45:06 2016 +0300 qemu: add capability check for memballoon 'deflate-on-oom' feature Add appropriate capability check and new virQEMUCaps flag for the new virtio balloon feature. QEMU commit with the complete feature description: http://git.qemu.org/?p=qemu.git;a=commit;h=e3816255bf4b6377bb405331e2ee0dc14d841b80 commit 7bf3198df685417783343bed03c2b3a0e1f69ea8 Author: Dmitry Andreev <dandreev@xxxxxxxxxxxxx> Date: Fri Jan 8 13:45:05 2016 +0300 conf: introduce 'autodeflate' attribute for memballoon device Excessive memory balloon inflation can cause invocation of OOM-killer, when Linux is under severe memory pressure. QEMU memballoon device has a feature to release some memory at the last moment before some process will be get killed by OOM-killer. Introduce a new optional balloon device attribute 'autodeflate' to enable or disable this feature. commit 2eb7a975756d05a5b54ab4acf60083beb6161ac6 Author: Cole Robinson <crobinso@xxxxxxxxxx> Date: Mon Jan 11 20:13:38 2016 -0500 rpc: socket: Don't repeatedly attempt to launch daemon On every socket connect(2) attempt we were re-launching session libvirtd, up to 100 times in 5 seconds. This understandably caused some weird load races and intermittent qemu:///session startup failures https://bugzilla.redhat.com/show_bug.cgi?id=1271183 commit 8da02d528068942303923fc4f935e77cccac9c7c Author: Cole Robinson <crobinso@xxxxxxxxxx> Date: Mon Jan 11 20:08:45 2016 -0500 rpc: socket: Explicitly error if we exceed retry count When we autolaunch libvirtd for session URIs, we spin in a retry loop waiting for the daemon to start and the connect(2) to succeed. However if we exceed the retry count, we don't explicitly raise an error, which can yield a slew of different error messages elsewhere in the code. Explicitly raise the last connect(2) failure if we run out of retries. commit f102c7146ed7f6e04af0ad3bce302476239f2502 Author: Cole Robinson <crobinso@xxxxxxxxxx> Date: Mon Jan 11 20:01:24 2016 -0500 rpc: socket: Minor cleanups - Add some debugging - Make the loop dependent only on retries - Make it explicit that connect(2) success exits the loop - Invert the error checking logic commit bc451c49805d067b2074ab18adf4d7b39d6ee3a2 Author: Roman Bogorodskiy <bogorodskiy@xxxxxxxxx> Date: Tue Jan 12 18:11:11 2016 +0300 Add missing virxdrdefs.h include to log_protocol Commit 2b6f6ad introduced the virxdrdefs.h header with common definitions to be included in the protocol files, but logging/log_protocol.x was missed, so add it there as well. Hopefully this fixes build on OS X. commit 46c551fdb41d4f1b8408b5d702df3b029b5906fe Author: Andrea Bolognani <abologna@xxxxxxxxxx> Date: Tue Jan 12 09:09:36 2016 +0100 virsh: Fix alignment in VIRSH_COMMON_OPT_CONFIG definition commit 133c511b5275cfd0a024fe0c62467f494dc62e40 Author: Ben Gray <ben.r.gray@xxxxxxxxx> Date: Thu Nov 26 16:10:40 2015 +0000 rpc: Don't rewrite msg->fds on every read dispatch When we are receiving data in smaller chunks it might happen that virNetServerClientDispatchRead() will be called multiple times. And as that happens, if it is a message that also transfer headers, we decode the number of them every single time and, unfortunately, also allocate the memory for them. That causes a leak, in the best scenario. Best viewed with '-w'. Signed-off-by: Martin Kletzander <mkletzan@xxxxxxxxxx> _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |