|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [xen-4.3-testing baseline-only test] 38617: regressions - FAIL
This run is configured for baseline tests only. flight 38617 xen-4.3-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/38617/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl 19 guest-start/debian.repeat fail REGR. vs. 38501 Regressions which are regarded as allowable (not blocking): test-amd64-amd64-migrupgrade 21 guest-migrate/src_host/dst_host fail like 38501 Tests which did not succeed, but are not blocking: test-amd64-amd64-rumpuserxen-amd64 1 build-check(1) blocked n/a test-amd64-i386-rumpuserxen-i386 1 build-check(1) blocked n/a build-amd64-rumpuserxen 6 xen-build fail never pass build-i386-rumpuserxen 6 xen-build fail never pass test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail never pass test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail never pass test-armhf-armhf-xl 6 xen-boot fail never pass test-armhf-armhf-libvirt-qcow2 6 xen-boot fail never pass test-armhf-armhf-xl-credit2 6 xen-boot fail never pass test-armhf-armhf-xl-vhd 6 xen-boot fail never pass test-armhf-armhf-xl-midway 6 xen-boot fail never pass test-armhf-armhf-libvirt 6 xen-boot fail never pass test-armhf-armhf-xl-multivcpu 6 xen-boot fail never pass test-armhf-armhf-libvirt-raw 6 xen-boot 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-xl-qemuu-win7-amd64 16 guest-stop fail never pass test-amd64-amd64-libvirt-vhd 11 migrate-support-check fail never pass test-amd64-amd64-xl-qemut-win7-amd64 16 guest-stop fail never pass test-amd64-i386-xend-qemut-winxpsp3 20 leak-check/check fail never pass test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail never pass test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop fail never pass version targeted for testing: xen ae05efd98917223a0e669026baceb7f489755a42 baseline version: xen 54dd84062d4e0f0298508826fc06990415da431e Last test of basis 38501 2015-12-11 15:50:08 Z 31 days Testing same since 38617 2016-01-11 05:55:51 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Dario Faggioli <dario.faggioli@xxxxxxxxxx> Ian Campbell <ian.campbell@xxxxxxxxxx> Ian Jackson <ian.jackson@xxxxxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> Wei Liu <wei.liu2@xxxxxxxxxx> jobs: build-amd64 pass build-armhf pass build-i386 pass build-amd64-libvirt pass build-armhf-libvirt pass build-i386-libvirt pass build-amd64-prev pass build-i386-prev pass build-amd64-pvops pass build-armhf-pvops pass build-i386-pvops pass build-amd64-rumpuserxen fail build-i386-rumpuserxen fail test-amd64-amd64-xl fail test-armhf-armhf-xl fail test-amd64-i386-xl pass test-amd64-i386-qemut-rhel6hvm-amd pass test-amd64-i386-qemuu-rhel6hvm-amd pass test-amd64-amd64-xl-qemut-debianhvm-amd64 pass test-amd64-i386-xl-qemut-debianhvm-amd64 pass test-amd64-amd64-xl-qemuu-debianhvm-amd64 pass test-amd64-i386-xl-qemuu-debianhvm-amd64 pass test-amd64-i386-freebsd10-amd64 pass test-amd64-amd64-xl-qemuu-ovmf-amd64 fail test-amd64-i386-xl-qemuu-ovmf-amd64 fail test-amd64-amd64-rumpuserxen-amd64 blocked test-amd64-amd64-xl-qemut-win7-amd64 fail test-amd64-i386-xl-qemut-win7-amd64 fail test-amd64-amd64-xl-qemuu-win7-amd64 fail test-amd64-i386-xl-qemuu-win7-amd64 fail test-amd64-amd64-xl-credit2 pass test-armhf-armhf-xl-credit2 fail test-amd64-i386-freebsd10-i386 pass test-amd64-i386-rumpuserxen-i386 blocked test-amd64-i386-qemut-rhel6hvm-intel pass test-amd64-i386-qemuu-rhel6hvm-intel pass test-amd64-amd64-libvirt pass test-armhf-armhf-libvirt fail test-amd64-i386-libvirt pass test-armhf-armhf-xl-midway fail test-amd64-amd64-migrupgrade fail test-amd64-i386-migrupgrade pass test-amd64-amd64-xl-multivcpu pass test-armhf-armhf-xl-multivcpu fail test-amd64-amd64-pair pass test-amd64-i386-pair pass test-amd64-amd64-pv pass test-amd64-i386-pv pass test-amd64-amd64-amd64-pvgrub pass test-amd64-amd64-i386-pvgrub pass test-amd64-amd64-pygrub pass test-armhf-armhf-libvirt-qcow2 fail test-amd64-amd64-xl-qcow2 pass test-armhf-armhf-libvirt-raw fail test-amd64-i386-xl-raw pass test-amd64-i386-xl-qemut-winxpsp3-vcpus1 pass test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 pass test-amd64-amd64-libvirt-vhd pass test-armhf-armhf-xl-vhd fail test-amd64-i386-xend-qemut-winxpsp3 fail test-amd64-amd64-xl-qemut-winxpsp3 pass test-amd64-amd64-xl-qemuu-winxpsp3 pass ------------------------------------------------------------ sg-report-flight on osstest.xs.citrite.net logs: /home/osstest/logs images: /home/osstest/images Logs, config files, etc. are available at http://osstest.xs.citrite.net/~osstest/testlogs/logs Test harness code can be found at http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary Push not applicable. ------------------------------------------------------------ commit ae05efd98917223a0e669026baceb7f489755a42 Author: Wei Liu <wei.liu2@xxxxxxxxxx> Date: Wed Oct 14 12:41:13 2015 +0100 Config.mk: update OVMF changeset Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx> Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx> (cherry picked from commits 04c5efb0a141fa53e805e396970419436e74ce67 and f046e501bbca1c8a46853b2e1f1b587e228c73de) Apropos of discussion in "OVMF related osstest failures on multiple branches" http://lists.xenproject.org/archives/html/xen-devel/2016-01/msg00442.html We believe the older ovmf.git does not work when built with the gcc in Debian jessie. We do not know where this bug lies but we are fixing it by updating ovmf. We have decided that we are not in a position to review the changes to OVMF upstream, and ourselves decide what to cherry pick. Instead we will update the revision wholesale and use the xen.git stable branches' push gate. Conflicts: Config.mk Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> (cherry picked from commits 6c3c6ff9ecaa5ee0be8b535d36fdcd12380564a1 and 1d3cc6e62c4d2fc3dd9251d4921881425c9d27bd) Conflicts: Config.mk Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> (cherry picked from commit ee576d71103e6795dc0add91db1b0d281eab1caf) Conflicts: Config.mk Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> (cherry picked from commit 6d2c41d676339ecc6255b92876b6153d4f85f579) In 4.3, old OVMF_UPSTREAM_REVISION was b0855f92 rather than cb9a7eba. I have pulled in the additional changes, willy-nilly. Conflicts: Config.mk Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> commit a64bfae49ae845ba4cb8cb6923fa08c41439872a Author: Dario Faggioli <dario.faggioli@xxxxxxxxxx> Date: Fri Jun 20 16:09:00 2014 +0200 blktap: Fix two 'maybe uninitialized' variables [ Cross-ported to blktap1 from 345e44a85d71a "blktap2: Fix two 'maybe uninitialized' variables" -iwj; Remainder of commit message is from blktap2's version. ] for which gcc 4.9.0 complains about, like this: block-qcow.c: In function `get_cluster_offset': block-qcow.c:431:3: error: `tmp_ptr' may be used uninitialized in this function [-Werror=maybe-uninitialized] memcpy(tmp_ptr, l1_ptr, 4096); ^ block-qcow.c:606:7: error: `tmp_ptr2' may be used uninitialized in this function [-Werror=maybe-uninitialized] if (write(s->fd, tmp_ptr2, 4096) != 4096) { ^ cc1: all warnings being treated as errors /home/dario/Sources/xen/xen/xen.git/tools/blktap2/drivers/../../../tools/Rules.mk:89: recipe for target 'block-qcow.o' failed make[5]: *** [block-qcow.o] Error 1 The proper behavior is to return upon allocation failure. About what to return, 0 seems the best option, looking at both the function and the call sites. Signed-off-by: Dario Faggioli <dario.faggioli@xxxxxxxxxx> Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> Backport-requested-by: Ian Campbell <ian.campbell@xxxxxxxxxx> Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> (cherry picked from commit 845e8c1653242bbd9b9de5a081182db0f3f39054) (cherry picked from commit e003d429d8c63523df40663b4586c572ce796659) commit 0fe03d7ed26d41e9434fb007d6fe4d05077efa7d Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> Date: Mon Jan 4 15:36:53 2016 +0000 QEMU_TAG update commit 0574a773238f0ecce3873dc525082f6e16ac655b Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> Date: Fri Dec 18 14:59:01 2015 +0000 QEMU_TAG update commit 83349eede062fc636f89657628a772438012673a Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Thu Dec 17 14:33:22 2015 +0100 x86/HVM: avoid reading ioreq state more than once Otherwise, especially when the compiler chooses to translate the switch() to a jump table, unpredictable behavior (and in the jump table case arbitrary code execution) can result. This is XSA-166. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx> master commit: b452430a4cdfc801fa4bc391aed7522365e1deb6 master date: 2015-12-17 14:22:46 +0100 commit f5119912e9a5f888273306ff6b462d6fd1f7a6bd Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Thu Dec 17 14:32:56 2015 +0100 x86: don't leak ST(n)/XMMn values to domains first using them FNINIT doesn't alter these registers, and hence using it is insufficient to initialize a guest's initial state. This is CVE-2015-8555 / XSA-165. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: 81818b3f277544535974204f8d840da86fa8a44f master date: 2015-12-17 14:22:13 +0100 ======================================== commit b96625e17169a7958575c2fb41499bb9ea2c212e Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Mon Jan 4 15:34:29 2016 +0000 MSI-X: avoid array overrun upon MSI-X table writes pt_msix_init() allocates msix->msix_entry[] to just cover msix->total_entries entries. While pci_msix_readl() resorts to reading physical memory for out of bounds reads, pci_msix_writel() so far simply accessed/corrupted unrelated memory. pt_iomem_map()'s call to cpu_register_physical_memory() registers a page granular region, which is necessary as the Pending Bit Array may share space with the MSI-X table (but nothing else is allowed to). This also explains why pci_msix_readl() actually honors out of bounds reads, but pci_msi_writel() doesn't need to. This is XSA-164. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx> (cherry picked from commit 569eac99e8ddccd15fe78e8a3af5622afe780e3b) (cherry picked from commit 7457f4beae2583a106a4176949514e81248fc22d) (cherry picked from commit f5bf3ed6eaa752d91e4d1fb1675b4c3e9f984c71) (cherry picked from commit 2bbe49494f5e910c6fb49f6800d143cae9eb5758) commit 95872ff9713292f1c859c093feae0a2eaff8f810 Author: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> Date: Fri Nov 20 10:56:00 2015 -0500 blkif: Avoid double access to src->nr_segments src is stored in shared memory and src->nr_segments is dereferenced twice at the end of the function. If a compiler decides to compile this into two separate memory accesses then the size limitation could be bypassed. Fix it by removing the double access to src->nr_segments. This is part of XSA-155. Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> commit 806a941fb5c68f0b25f209b92553acb298d30c04 Author: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> Date: Fri Nov 20 10:37:08 2015 -0500 xenfb: avoid reading twice the same fields from the shared page Reading twice the same field could give the guest an attack of opportunity. In the case of event->type, gcc could compile the switch statement into a jump table, effectively ending up reading the type field multiple times. This is part of XSA-155. Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> _______________________________________________ osstest-output mailing list osstest-output@xxxxxxxxxxxxxxxxxxxx http://lists.xenproject.org/cgi-bin/mailman/listinfo/osstest-output
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |