[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [libvirt test] 121735: regressions - FAIL
flight 121735 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/121735/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-arm64-arm64-libvirt-qcow2 10 debian-di-install fail REGR. vs. 121707 Tests which did not succeed, but are not blocking: test-armhf-armhf-libvirt-xsm 14 saverestore-support-check fail like 121707 test-armhf-armhf-libvirt 14 saverestore-support-check fail like 121707 test-armhf-armhf-libvirt-raw 13 saverestore-support-check fail like 121707 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-xsm 13 migrate-support-check fail never pass test-amd64-i386-libvirt 13 migrate-support-check fail never pass test-arm64-arm64-libvirt 13 migrate-support-check fail never pass 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-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-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 849b6a7b6a2fa8207af0ff1160edc8baf109213a baseline version: libvirt 439c27b1ae35e0daab6e86fc6320ea1682a3aabd Last test of basis 121707 2018-04-02 04:20:30 Z 2 days Testing same since 121735 2018-04-03 04:27:24 Z 1 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: John Ferlan <jferlan@xxxxxxxxxx> Kashyap Chamarthy <kchamart@xxxxxxxxxx> jobs: build-amd64-xsm pass build-arm64-xsm pass build-armhf-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 pass 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 pass test-amd64-amd64-libvirt-xsm pass test-arm64-arm64-libvirt-xsm pass test-armhf-armhf-libvirt-xsm pass test-amd64-i386-libvirt-xsm pass test-amd64-amd64-libvirt pass test-arm64-arm64-libvirt pass 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 fail 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 849b6a7b6a2fa8207af0ff1160edc8baf109213a Author: John Ferlan <jferlan@xxxxxxxxxx> Date: Sat Mar 10 08:47:44 2018 -0500 lxc: Use virDomainObjEndAPI after FindByName For consistency, rather than open coding the Unref and Unlock, just use the virDomainObjEndAPI API. Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx> commit bb0e0bcf6a0d785df7063cb6118b3a25f2a24d55 Author: Kashyap Chamarthy <kchamart@xxxxxxxxxx> Date: Mon Mar 26 12:53:12 2018 +0200 docs: formatdomain: Clarify CPU feature policy option "require" Using the 'require' value for the 'policy' attribute indicates that the guest will have the feature so the host CPU does not need to support it if the hypervisor can emulate it. E.g. 'x2apic' is emulated by QEMU even if the host does not support it: <feature policy='require' name='x2apic'/> Signed-off-by: Kashyap Chamarthy <kchamart@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 |