All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: ian.jackson@eu.citrix.com, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [xen-4.2-testing test] 14398: trouble: broken/fail/pass
Date: Thu, 15 Nov 2012 12:43:46 +0000	[thread overview]
Message-ID: <50A4F19202000078000A8DD1@nat28.tlf.novell.com> (raw)
In-Reply-To: <osstest-14398-mainreport@xen.org>

>>> On 15.11.12 at 13:04, xen.org <ian.jackson@eu.citrix.com> wrote:
> flight 14398 xen-4.2-testing real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/14398/ 
> 
> Failures and problems with tests :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-amd64-i386-pair         4 host-install/dst_host(4) broken REGR. vs. 14393

Is that a random failure, or infrastructure related? "Autopartitioning
using LVM failed because an error occurred while creating the volume
group" doesn't sound like something under our control...

Jan

  reply	other threads:[~2012-11-15 12:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-15 12:04 [xen-4.2-testing test] 14398: trouble: broken/fail/pass xen.org
2012-11-15 12:43 ` Jan Beulich [this message]
2012-11-15 12:54   ` 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=50A4F19202000078000A8DD1@nat28.tlf.novell.com \
    --to=jbeulich@suse.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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.