All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: "xen.org" <Ian.Jackson@eu.citrix.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	xen-devel@lists.xensource.com
Subject: Re: [linux-linus test] 25753: regressions - trouble: blocked/broken/fail/pass
Date: Mon, 7 Apr 2014 15:02:06 +0100	[thread overview]
Message-ID: <5342AFDE.7000400@citrix.com> (raw)
In-Reply-To: <osstest-25753-mainreport@xen.org>

On 05/04/14 02:41, xen.org wrote:
> flight 25753 linux-linus real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/25753/
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-amd64-i386-rhel6hvm-amd  5 xen-boot                  fail REGR. vs. 12557
>  test-amd64-i386-qemuu-rhel6hvm-amd  5 xen-boot            fail REGR. vs. 12557
>  test-amd64-i386-xl-multivcpu  5 xen-boot                  fail REGR. vs. 12557
>  test-amd64-i386-xl            5 xen-boot                  fail REGR. vs. 12557
>  test-amd64-i386-xl-credit2    5 xen-boot                  fail REGR. vs. 12557
>  test-amd64-i386-xl-winxpsp3-vcpus1  5 xen-boot            fail REGR. vs. 12557
>  test-amd64-i386-pair          8 xen-boot/dst_host         fail REGR. vs. 12557
>  test-amd64-i386-pair          7 xen-boot/src_host         fail REGR. vs. 12557

Linux is currently broken for 32-bit x86 PV guests due to some changes
to the kernel/irq stacks.  I think Boris is investigating.

I don't know if this explains these failures.  It's not obvious what the
test name translates to.

David

  reply	other threads:[~2014-04-07 14:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-05  1:41 [linux-linus test] 25753: regressions - trouble: blocked/broken/fail/pass xen.org
2014-04-07 14:02 ` David Vrabel [this message]
2014-04-07 14:40   ` Ian Campbell
2014-04-07 14:59   ` 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=5342AFDE.7000400@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=boris.ostrovsky@oracle.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.