From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "xen.org" <Ian.Jackson@eu.citrix.com>, xen-devel@lists.xensource.com
Subject: Re: [xen-4.4-testing test] 30367: regressions - FAIL
Date: Wed, 24 Sep 2014 10:21:54 +0100 [thread overview]
Message-ID: <54228D32.2060803@citrix.com> (raw)
In-Reply-To: <osstest-30367-mainreport@xen.org>
On 24/09/14 08:20, xen.org wrote:
> flight 30367 xen-4.4-testing real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/30367/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-xl-win7-amd64 7 windows-install fail REGR. vs. 30239
Can we just nuke this test? It has never worked reliably, and now only
serves to delay movement from staging-4.4 to stable-4.4
~Andrew
>
> 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
> test-amd64-i386-libvirt 9 guest-start fail never pass
> test-amd64-amd64-libvirt 9 guest-start fail never pass
> test-armhf-armhf-xl 10 migrate-support-check fail never pass
> test-armhf-armhf-libvirt 9 guest-start fail never pass
> test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass
> build-amd64-rumpuserxen 6 xen-build fail never pass
> build-i386-rumpuserxen 6 xen-build fail never pass
> test-amd64-amd64-xl-qemut-win7-amd64 14 guest-stop fail never pass
> test-amd64-i386-xend-qemut-winxpsp3 17 leak-check/check fail never pass
> test-amd64-amd64-xl-qemut-winxpsp3 14 guest-stop fail never pass
> test-amd64-i386-xl-qemuu-win7-amd64 14 guest-stop fail never pass
> test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 14 guest-stop fail never pass
> test-amd64-amd64-xl-qemuu-winxpsp3 14 guest-stop fail never pass
> test-amd64-i386-xend-winxpsp3 17 leak-check/check fail never pass
> test-amd64-i386-xl-qemut-winxpsp3-vcpus1 14 guest-stop fail never pass
> test-amd64-amd64-xl-qemuu-win7-amd64 14 guest-stop fail never pass
> test-amd64-i386-xl-winxpsp3-vcpus1 14 guest-stop fail never pass
> test-amd64-i386-xl-win7-amd64 14 guest-stop fail never pass
> test-amd64-i386-xl-qemut-win7-amd64 14 guest-stop fail never pass
> test-amd64-amd64-xl-winxpsp3 14 guest-stop fail never pass
>
> version targeted for testing:
> xen a299a3e88a387de88489d6a6f61bebdafc95ebe5
> baseline version:
> xen be84c34e642f06107be8096b7e90dd0c86f13164
>
> ------------------------------------------------------------
> People who touched revisions under test:
> Andrei LUTAS <vlutas@bitdefender.com>
> Andrew Cooper <andrew.cooper3@citrix.com>
> Jan Beulich <jbeulich@suse.com>
> Keir Fraser <keir@xen.org>
> ------------------------------------------------------------
>
> jobs:
> build-amd64-xend pass
> build-i386-xend 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
> build-amd64-rumpuserxen fail
> build-i386-rumpuserxen fail
> test-amd64-amd64-xl pass
> test-armhf-armhf-xl pass
> test-amd64-i386-xl pass
> test-amd64-i386-rhel6hvm-amd 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 pass
> test-amd64-i386-xl-qemuu-ovmf-amd64 pass
> 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-win7-amd64 fail
> test-amd64-i386-xl-win7-amd64 fail
> test-amd64-i386-xl-credit2 pass
> test-amd64-i386-freebsd10-i386 pass
> test-amd64-i386-rumpuserxen-i386 blocked
> test-amd64-amd64-xl-pcipt-intel fail
> test-amd64-i386-rhel6hvm-intel pass
> test-amd64-i386-qemut-rhel6hvm-intel pass
> test-amd64-i386-qemuu-rhel6hvm-intel pass
> test-amd64-amd64-libvirt fail
> test-armhf-armhf-libvirt fail
> test-amd64-i386-libvirt fail
> test-amd64-i386-xl-multivcpu pass
> test-amd64-amd64-pair pass
> test-amd64-i386-pair pass
> test-amd64-amd64-xl-sedf-pin pass
> test-amd64-amd64-pv pass
> test-amd64-i386-pv pass
> test-amd64-amd64-xl-sedf pass
> test-amd64-i386-xl-qemut-winxpsp3-vcpus1 fail
> test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 fail
> test-amd64-i386-xl-winxpsp3-vcpus1 fail
> test-amd64-i386-xend-qemut-winxpsp3 fail
> test-amd64-amd64-xl-qemut-winxpsp3 fail
> test-amd64-amd64-xl-qemuu-winxpsp3 fail
> test-amd64-i386-xend-winxpsp3 fail
> test-amd64-amd64-xl-winxpsp3 fail
>
>
> ------------------------------------------------------------
> sg-report-flight on osstest.cam.xci-test.com
> logs: /home/xc_osstest/logs
> images: /home/xc_osstest/images
>
> Logs, config files, etc. are available at
> http://www.chiark.greenend.org.uk/~xensrcts/logs
>
> Test harness code can be found at
> http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
>
>
> Not pushing.
>
> ------------------------------------------------------------
> commit a299a3e88a387de88489d6a6f61bebdafc95ebe5
> Author: Jan Beulich <jbeulich@suse.com>
> Date: Tue Sep 23 14:40:51 2014 +0200
>
> x86emul: only emulate software interrupt injection for real mode
>
> Protected mode emulation currently lacks proper privilege checking of
> the referenced IDT entry, and there's currently no legitimate way for
> any of the respective instructions to reach the emulator when the guest
> is in protected mode.
>
> This is XSA-106.
>
> Reported-by: Andrei LUTAS <vlutas@bitdefender.com>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> Acked-by: Keir Fraser <keir@xen.org>
> master commit: 346d4545569928b652c40c7815c1732676f8587c
> master date: 2014-09-23 14:33:50 +0200
>
> commit 510f1717827b54e27acd86e1781bb472a10cc72a
> Author: Andrew Cooper <andrew.cooper3@citrix.com>
> Date: Tue Sep 23 14:40:12 2014 +0200
>
> x86/emulate: check cpl for all privileged instructions
>
> Without this, it is possible for userspace to load its own IDT or GDT.
>
> This is XSA-105.
>
> Reported-by: Andrei LUTAS <vlutas@bitdefender.com>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> Tested-by: Andrei LUTAS <vlutas@bitdefender.com>
> Reviewed-by: Jan Beulich <jbeulich@suse.com>
> master commit: 0e442727ceccfa32a7276cccd205b4722e68fdc1
> master date: 2014-09-23 14:33:06 +0200
>
> commit 20429b1274fe9ed0b40e73c295fa79b70c1bf80e
> Author: Andrew Cooper <andrew.cooper3@citrix.com>
> Date: Tue Sep 23 14:39:05 2014 +0200
>
> x86/shadow: fix race condition sampling the dirty vram state
>
> d->arch.hvm_domain.dirty_vram must be read with the domain's paging lock held.
>
> If not, two concurrent hypercalls could both end up attempting to free
> dirty_vram (the second of which will free a wild pointer), or both end up
> allocating a new dirty_vram structure (the first of which will be leaked).
>
> This is XSA-104.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> Reviewed-by: Tim Deegan <tim@xen.org>
> master commit: 46a49b91f1026f64430b84dd83e845a33f06415e
> master date: 2014-09-23 14:31:47 +0200
> (qemu changes not included)
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-09-24 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 7:20 [xen-4.4-testing test] 30367: regressions - FAIL xen.org
2014-09-24 9:21 ` Andrew Cooper [this message]
2014-09-24 9:25 ` Ian Campbell
2014-09-24 10:15 ` Andrew Cooper
2014-09-24 14:14 ` Ian Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54228D32.2060803@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.