|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [libvirt test] 105805: regressions - FAIL
flight 105805 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/105805/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-libvirt-pair 9 xen-boot/src_host fail REGR. vs. 105785 Regressions which are regarded as allowable (not blocking): test-armhf-armhf-libvirt-xsm 13 saverestore-support-check fail like 105785 test-armhf-armhf-libvirt 13 saverestore-support-check fail like 105785 test-armhf-armhf-libvirt-raw 12 saverestore-support-check fail like 105785 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 test-amd64-amd64-libvirt-xsm 12 migrate-support-check fail never pass test-amd64-i386-libvirt-xsm 12 migrate-support-check fail never pass test-amd64-i386-libvirt 12 migrate-support-check fail never pass test-amd64-amd64-libvirt 12 migrate-support-check fail never pass build-arm64 5 xen-build fail never pass build-arm64-xsm 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 build-arm64-pvops 5 kernel-build fail never pass test-armhf-armhf-libvirt-xsm 12 migrate-support-check fail never pass test-armhf-armhf-libvirt 12 migrate-support-check fail never pass test-armhf-armhf-libvirt-raw 11 migrate-support-check fail never pass version targeted for testing: libvirt ec94e14b681a671776c8d7ca962d3d7ed5aca5b7 baseline version: libvirt 723fef99c0e29d1a327aaea4cef477609f6ccbc2 Last test of basis 105785 2017-02-14 04:20:10 Z 1 days Testing same since 105805 2017-02-15 04:21:42 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Andrea Bolognani <abologna@xxxxxxxxxx> Jim Fehlig <jfehlig@xxxxxxxx> Jiri Denemark <jdenemar@xxxxxxxxxx> Ján Tomko <jtomko@xxxxxxxxxx> Tomáš Golembiovský <tgolembi@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 pass 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 fail 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 Not pushing. ------------------------------------------------------------ commit ec94e14b681a671776c8d7ca962d3d7ed5aca5b7 Author: Jim Fehlig <jfehlig@xxxxxxxx> Date: Thu Feb 2 19:26:13 2017 -0700 apparmor: don't fail on non-apparmor <seclabel> If the apparmor security driver is loaded/enabled and domain config contains a <seclabel> element whose type attribute is not 'apparmor', starting the domain fails when attempting to label resources such as tap FDs. Many of the apparmor driver entry points attempt to retrieve the apparmor security label from the domain def, returning failure if not found. Functions such as AppArmorSetFDLabel fail even though domain config contains an explicit 'none' secuirty driver, e.g. <seclabel type='none' model='none'/> Change the entry points to succeed if the domain config <seclabel> is not apparmor. This matches the behavior of the selinux driver. commit 5cdfc80ba88e8856fbebe78e850b39807ed9b811 Author: Jim Fehlig <jfehlig@xxxxxxxx> Date: Thu Feb 2 19:17:29 2017 -0700 apparmor: don't overwrite error from reload_profile Like other callers of reload_profile, don't overwrite errors in AppArmorSetSecurityHostdevLabelHelper. commit 598b6d79997421da33aefc98f5f5889cf9798b1b Author: Jiri Denemark <jdenemar@xxxxxxxxxx> Date: Mon Feb 13 09:32:21 2017 +0100 qemu_monitor_json: Properly check GetArray return value Commit 2a8d40f4ec refactored qemuMonitorJSONGetCPUx86Data and replaced virJSONValueObjectGet(reply, "return") with virJSONValueObjectGetArray. While the former is guaranteed to always return non-NULL pointer the latter may return NULL if the returned JSON object is not an array. Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx> commit ee6ec7824d168cfa28bd67f99772aa0a51473bb3 Author: Andrea Bolognani <abologna@xxxxxxxxxx> Date: Tue Feb 14 15:46:23 2017 +0100 qemu: Call chmod() after mknod() mknod() is affected my the current umask, so we're not guaranteed the newly-created device node will have the right permissions. Call chmod(), which is not affected by the current umask, immediately afterwards to solve the issue. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1421036 commit e04bd5b6fccbbcb664b9af545fb5c4da3ead4c28 Author: Andrea Bolognani <abologna@xxxxxxxxxx> Date: Tue Feb 14 14:42:54 2017 +0100 spec: Require libacl when building the QEMU driver For the namespaces feature to work properly we need to be able to make a perfect copy of the original /dev, including ACLs. By adding a BuildRequires on libacl-devel we ensure that ACL support will be enabled at configure time and made available to the QEMU driver. commit c315ead7020bde429fe61bf496686f125ac4c882 Author: Andrea Bolognani <abologna@xxxxxxxxxx> Date: Tue Feb 14 15:21:29 2017 +0100 configure: Move ACL checks to a separate file commit 4a41cf18b1356118e64c431ab551f63e12d3fb64 Author: Ján Tomko <jtomko@xxxxxxxxxx> Date: Mon Jan 30 13:52:02 2017 +0100 util: fix off-by-one when expanding a bitmap To make sure bit 'b' fits into the bitmap, we need to allocate b+1 bits, since we number from 0. Adjust the bitmap test to set a bit at a multiple of 16. That way the test fails without this fix, because the VIR_REALLOC call clears the newly added memory even if the original pointer has not changed. commit 5d82a2085ffbae89ece9a11a67e561e43834f5b1 Author: Tomáš Golembiovský <tgolembi@xxxxxxxxxx> Date: Mon Feb 13 23:49:06 2017 +0100 valgrind: add suppression for bash memory leak Add suppression for memory leak in bash observerd with bash 4.4.011 on Arch Linux. Signed-off-by: Tomáš Golembiovský <tgolembi@xxxxxxxxxx> _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |