From: Wei Liu <wei.liu2@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Ian.Jackson@citrix.com, xen-devel@lists.xensource.com,
wei.liu2@citrix.com,
osstest service owner <osstest-admin@xenproject.org>
Subject: Re: [xen-unstable test] 65066: regressions - FAIL
Date: Wed, 25 Nov 2015 10:13:03 +0000 [thread overview]
Message-ID: <20151125101303.GB15747@citrix.com> (raw)
In-Reply-To: <1448444036.17688.7.camel@citrix.com>
On Wed, Nov 25, 2015 at 09:33:56AM +0000, Ian Campbell wrote:
> On Wed, 2015-11-25 at 02:30 +0000, osstest service owner wrote:
> > flight 65066 xen-unstable real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/65066/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> > test-amd64-i386-rumpuserxen-i386 10 guest-start fail REGR. vs. 64035
>
> We discussed this possibility IRL when the "minios: don't rely on specific
> page table allocation scheme" fix was being made for the issue exposed by
> the changes to the domain builder to support larger guests.
>
> The rumpkernel flights have been disabled for a while now pending a
> reworking of osstest to cope with an upstream change to the build system,
> so there is no possibility, at the moment, of getting the mini-os fix into
> upstream rump and then through our rumpkernel push gate and into the xen-
> unstable tests.
>
> Therefore I believe we concluded we would force push this failure.
>
> But before I did so I just wanted to confirm I'd understood the plan.
>
Yes. Force push please. This failure is expected.
Wei.
next prev parent reply other threads:[~2015-11-25 10:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 2:30 [xen-unstable test] 65066: regressions - FAIL osstest service owner
2015-11-25 9:33 ` Ian Campbell
2015-11-25 9:43 ` Andrew Cooper
2015-11-25 10:13 ` Wei Liu [this message]
2015-11-25 10:33 ` Ian Campbell
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=20151125101303.GB15747@citrix.com \
--to=wei.liu2@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=osstest-admin@xenproject.org \
--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.