From: Wei Liu <wei.liu2@citrix.com>
To: osstest service owner <osstest-admin@xenproject.org>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
xen-devel@lists.xensource.com, wei.liu2@citrix.com,
Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [xen-4.6-testing test] 65327: regressions - FAIL
Date: Fri, 4 Dec 2015 10:20:18 +0000 [thread overview]
Message-ID: <20151204102018.GB5675@citrix.com> (raw)
In-Reply-To: <osstest-65327-mainreport@xen.org>
On Fri, Dec 04, 2015 at 05:15:28AM +0000, osstest service owner wrote:
> flight 65327 xen-4.6-testing real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/65327/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 16 guest-localmigrate/x10 fail in 65210 REGR. vs. 63449
This has been blocked on merlot* for quite a while.
And xen-unstable (with the supposedly fixes to mini-os and oxenstored in
place) is not doing any better on merlot*, just that the test cast
itself won't block pushing.
http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm/ALL
Looking into this further, OSStest is using cxenstored, which supposedly
doesn't have the bug that stalled the ring.
Maybe this is a host specific bug. Maybe cxenstored also has a latent
bug. I'm not sure. I don't know what to make of this.
Wei.
next prev parent reply other threads:[~2015-12-04 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 5:15 [xen-4.6-testing test] 65327: regressions - FAIL osstest service owner
2015-12-04 10:20 ` Wei Liu [this message]
2015-12-04 11:14 ` Jan Beulich
2015-12-04 12:14 ` Ian Jackson
2015-12-04 12:15 ` [xen-4.6-testing test] 65327: regressions - FAIL [and 1 more messages] 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=20151204102018.GB5675@citrix.com \
--to=wei.liu2@citrix.com \
--cc=Ian.Jackson@eu.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.