All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	ian.jackson@eu.citrix.com, David Vrabel <david.vrabel@citrix.com>
Subject: Re: [xen-4.4-testing test] 33394: regressions - FAIL
Date: Wed, 14 Jan 2015 09:52:50 +0000	[thread overview]
Message-ID: <1421229170.19103.181.camel@citrix.com> (raw)
In-Reply-To: <54B641080200007800054A5F@mail.emea.novell.com>

On Wed, 2015-01-14 at 09:12 +0000, Jan Beulich wrote:
> >>> On 13.01.15 at 21:30, <Ian.Jackson@eu.citrix.com> wrote:
> > flight 33394 xen-4.4-testing real [real]
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/33394/ 
> > 
> > Regressions :-(
> > 
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> >  test-amd64-i386-xl-qemut-winxpsp3-vcpus1  5 xen-boot      fail REGR. vs. 33292
> 
> In all recent xen-boot failures I looked at the boot process seems
> stalled starting ntpd - is that perhaps infrastructure related?

That's not impossible, I'd suspect DNS related. Hopefully all this sort
of thing will be much better (or at least under our control) in the new
colo.

> >  test-amd64-i386-pair   17 guest-migrate/src_host/dst_host fail REGR. vs. 33292
> 
> Both involved hosts appear to still be affected by the swiotlb issue
> - wasn't that supposed to long be addressed?

The patches to increase the swiotlb size in osstest didn't help, I
think.

David V posted some patches upstream to fix the problem at the root, but
I don't remember seeing any responses from the upstream maintainers
(they touched some common and/or x86 code IIRC)

Ian.

  reply	other threads:[~2015-01-14  9:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 20:30 [xen-4.4-testing test] 33394: regressions - FAIL xen.org
2015-01-14  9:12 ` Jan Beulich
2015-01-14  9:52   ` Ian Campbell [this message]
2015-01-14 12:00     ` David Vrabel

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=1421229170.19103.181.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=david.vrabel@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.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.