|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [libvirt test] 104804: regressions - trouble: blocked/broken/fail/pass
flight 104804 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/104804/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-libvirt 3 host-install(3) broken REGR. vs. 104685 test-amd64-amd64-libvirt-xsm 3 host-install(3) broken REGR. vs. 104685 test-armhf-armhf-libvirt 6 xen-boot fail REGR. vs. 104685 Regressions which are regarded as allowable (not blocking): test-armhf-armhf-libvirt-xsm 13 saverestore-support-check fail like 104685 test-armhf-armhf-libvirt-raw 12 saverestore-support-check fail like 104685 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 5 kernel-build fail never pass test-amd64-i386-libvirt-xsm 12 migrate-support-check fail never pass test-amd64-amd64-libvirt 12 migrate-support-check fail never pass build-arm64-xsm 5 xen-build fail never pass build-arm64 5 xen-build fail never pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 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-vhd 11 migrate-support-check fail never pass test-armhf-armhf-libvirt-xsm 12 migrate-support-check fail never pass test-armhf-armhf-libvirt-raw 11 migrate-support-check fail never pass version targeted for testing: libvirt bfc32e58955b297b447b0c94bb99be6fdcf5b8c1 baseline version: libvirt eebec1697e88080f5a1271d104083430e34c457f Last test of basis 104685 2017-01-26 04:20:47 Z 2 days Failing since 104742 2017-01-27 04:21:12 Z 1 days 2 attempts Testing same since 104804 2017-01-28 04:20:09 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: John Ferlan <jferlan@xxxxxxxxxx> Michal Privoznik <mprivozn@xxxxxxxxxx> Nitesh Konkar <niteshkonkar.libvirt@xxxxxxxxx> Nitesh Konkar <nitkon12@xxxxxxxxxxxxxxxxxx> Olga Krishtal <okrishtal@xxxxxxxxxxxxx> Pavel Hrdina <phrdina@xxxxxxxxxx> Peter Krempa <pkrempa@xxxxxxxxxx> jobs: build-amd64-xsm pass build-arm64-xsm fail build-armhf-xsm pass build-i386-xsm pass build-amd64 pass build-arm64 fail 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 fail 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 broken 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 fail test-amd64-i386-libvirt broken 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 test-amd64-i386-libvirt host-install(3) broken-step test-amd64-amd64-libvirt-xsm host-install(3) Not pushing. ------------------------------------------------------------ commit bfc32e58955b297b447b0c94bb99be6fdcf5b8c1 Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Fri Jan 27 10:39:53 2017 +0100 tests: storage: Fix storage xml2xml test for vstorage pool The input and output were the same, but the output file did not correspond to what libvirt would output. commit a7ae7ca9d4d94eaa67639dda200c711bcc46bb0a Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Fri Jan 27 10:37:56 2017 +0100 configure: Fix copy-paste error in vstorage backend check The 'fs' backend m4 code was copied, but one of the condition were not changed which resulted into: configure: Gluster: yes configure: ZFS: yes configure: Virtuozzo storage: check Make the code turn on the virtuozzo driver automatically if the tools are found. commit f19390d2d3ab18cc9bff53e1d642e4e2b534f5a5 Author: Pavel Hrdina <phrdina@xxxxxxxxxx> Date: Wed Jan 25 17:42:07 2017 +0100 domain_conf: vnc: preserve autoport value if no port was specified The issue is that if this graphics definition is provided: <graphics type='vnc' port='0'/> it's parsed as: <graphics type='vnc' autoport='no'> <listen type='address'/> </graphics> but if the resulting XML is parsed again the output is: <graphics type='vnc' port='-1' autoport='yes'> <listen type='address'/> </graphics> and this should not happen. The XML have to always remain the same after it was already parsed by libvirt. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1383039 Signed-off-by: Pavel Hrdina <phrdina@xxxxxxxxxx> commit 425a6837a6e87a15d1f3f802fe7b17e4e0dc5cae Author: Pavel Hrdina <phrdina@xxxxxxxxxx> Date: Wed Jan 25 10:49:16 2017 +0100 doc: improve VNC/SPICE password documentation If the passwd attribute is set to empty string it disables VNC/SPICE access to the guest. Signed-off-by: Pavel Hrdina <phrdina@xxxxxxxxxx> commit a4ec42805cef535e972b6754cdb5efd529600135 Author: Nitesh Konkar <niteshkonkar.libvirt@xxxxxxxxx> Date: Thu Jan 19 10:28:44 2017 +0530 virsh: Fix manpage typo Signed-off-by: Nitesh Konkar <nitkon12@xxxxxxxxxxxxxxxxxx> commit 1c1e6c1e18b733282f7b45fcb94ccbd1b61587df Author: Nitesh Konkar <niteshkonkar.libvirt@xxxxxxxxx> Date: Wed Jan 18 12:35:35 2017 +0530 virsh: Modify description for LIBVIRT_DEBUG=4 in manpage As LIBVIRT_DEBUG=4 logs only error messages and there are no levels above it, adjusting the description in the man page accordingly. Signed-off-by: Nitesh Konkar <nitkon12@xxxxxxxxxxxxxxxxxx> commit 67e98c6452550ea36396a77e651b43c50b1525b4 Author: Nitesh Konkar <niteshkonkar.libvirt@xxxxxxxxx> Date: Wed Jan 25 14:42:38 2017 +0530 virnettlssessiontest.c: fix grammar Signed-off-by: Nitesh Konkar <nitkon12@xxxxxxxxxxxxxxxxxx> commit 26ac16f3ce68961a2b90469b284ad6c07bdd6320 Author: Nitesh Konkar <niteshkonkar.libvirt@xxxxxxxxx> Date: Tue Jan 24 14:42:03 2017 +0530 perf: Prevent enabling of already enabled perf event Currently, on every --enable perf_event command, a new event->fd is created and counting of perf event counter starts from zero and previous event->fd is lost. This patch prevents this behaviour. Signed-off-by: Nitesh Konkar <nitkon12@xxxxxxxxxxxxxxxxxx> commit 4dd19ea91330678e67676aa85eecc56b5f2c8c51 Author: Nitesh Konkar <niteshkonkar.libvirt@xxxxxxxxx> Date: Sat Jan 21 20:08:29 2017 +0530 docs: Reword virsh manpage for --uuid --name --details options This commit is similar to commit 0977ada8.The virsh manpage lists options --uuid and --name as mutually exclusive if option --details is specified when actually the option --details is mutually exclusive and can't go with options --uuid and/or --name. This patch rewords the virsh manpage to state the correct meaning. Signed-off-by: Nitesh Konkar <nitkon12@xxxxxxxxxxxxxxxxxx> commit d18c083c39bb6650def0defe8ef513ffa3e197f6 Author: Olga Krishtal <okrishtal@xxxxxxxxxxxxx> Date: Thu Jan 26 19:44:26 2017 +0300 vstorage: Fix build Needed storage_util.h - missed while merging '5f07c3c07' with commit id '479a2f16'. Signed-off-by: Olga Krishtal <okrishtal@xxxxxxxxxxxxx> commit 448e2d5e94b2f082ecfd5697851c5d878fc75b15 Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Thu Jan 26 11:43:30 2017 -0500 storage: Fix build due to recent storage backend code movement Commit id '5f07c3c07' broke the freebsd build in the libvirt CI test environment because the UMOUNT was not defined unless WITH_STORAGE_FS is defined. So remove the virStorageBackendUmountLocal from storage_util.c,h and restore the code back in the storage_backend_fs.c and _vstorage.c modules. commit a55ddc87746d57f6e3d1f766cca6cb084dc3b0d2 Author: Olga Krishtal <okrishtal@xxxxxxxxxxxxx> Date: Tue Jan 17 17:10:59 2017 +0300 storage: vstorage pool documentation and simple test Signed-off-by: Olga Krishtal <okrishtal@xxxxxxxxxxxxx> commit 479a2f16f13f6023787766b2777e8506efa41a76 Author: Olga Krishtal <okrishtal@xxxxxxxxxxxxx> Date: Tue Jan 17 17:10:57 2017 +0300 storage: Introduce Virtuozzo vstorage pool and volume APIs Added create/define/etc pool operations for vstorage backend. Used the common/local pool API's from storage_util for operations that are not specific to vstorage. In particular Refresh and Delete Pool operations as well as all the Volume operations. Signed-off-by: Olga Krishtal <okrishtal@xxxxxxxxxxxxx> commit e590d5301e6bdcc74b733071b15745d44f58ecf4 Author: Olga Krishtal <okrishtal@xxxxxxxxxxxxx> Date: Tue Jan 17 17:10:55 2017 +0300 storage: Introduce Virtuozzo vstorage backend Added general definitions for vstorage pool backend including the build options to add --with-storage-vstorage checking. In order to use vstorage as a backend for a storage pool vstorage tools (vstorage and vstorage-mount) need to be installed. Signed-off-by: Olga Krishtal <okrishtal@xxxxxxxxxxxxx> commit 1452c85fb7391babe58b691838aef8c8868c8e10 Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Sat Jan 21 09:05:41 2017 -0500 storage: Create common file/dir volume backend helpers Move all the volume functions to storage_util to create local/common helpers using the same naming syntax as the existing upload, download, and wipe virStorageBackend*Local API's. In the process of doing so, found more API's that can now become local to storage_util. In order to distinguish between local/external - I changed the names of the now local only ones from "virStorageBackend..." to just "storageBackend..." Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx> commit 5f07c3c079d4db1bc3557f090800d6f0440285aa Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Wed Jan 18 14:17:21 2017 -0500 storage: Create common file/dir pool backend helpers Move some pool functions to storage_util to create local/common helpers using the same naming syntax as the existing upload, download, and wipe virStorageBackend*Local API's. In the process of doing so, found a few API's that can now become local to storage_util. In order to distinguish between local/external - I changed the names of the now local only ones from "virStorageBackend..." to just "storageBackend..." Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx> commit e26c21629e61e60611089fa86fb249a159bc1f37 Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Sat Jan 21 11:47:23 2017 -0500 storage: Move the virStorageBackendFileSystem{Start|Stop} API's Just moving code around with minor adjustment to have the Stop code combine with the Unmount code since all the Stop code did was call the Unmount code. commit 572eda12ad7336031fbbdc8c130c8674ba7764e8 Author: Michal Privoznik <mprivozn@xxxxxxxxxx> Date: Mon Jan 23 14:33:20 2017 +0100 qemu: Implement mtu on interface Not only we should set the MTU on the host end of the device but also let qemu know what MTU did we set. Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx> commit b020cf73fed761067c3b6196d993545f072c896f Author: Michal Privoznik <mprivozn@xxxxxxxxxx> Date: Mon Jan 23 14:32:13 2017 +0100 domain_conf: Introduce <mtu/> to <interface/> So far we allow to set MTU for libvirt networks. However, not all domain interfaces have to be plugged into a libvirt network and even if they are, they might want to have a different MTU (e.g. for testing purposes). Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx> _______________________________________________ osstest-output mailing list osstest-output@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/cgi-bin/mailman/listinfo/osstest-output
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |