From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, osstest-admin@xenproject.org
Subject: Re: [xen-4.3-testing test] 63948: regressions - FAIL
Date: Wed, 11 Nov 2015 11:51:43 +0000 [thread overview]
Message-ID: <1447242703.11601.37.camel@citrix.com> (raw)
In-Reply-To: <5643361F02000078000B3BCB@prv-mh.provo.novell.com>
On Wed, 2015-11-11 at 04:35 -0700, Jan Beulich wrote:
> > > > On 11.11.15 at 12:25, <ian.campbell@citrix.com> wrote:
> > On Wed, 2015-11-11 at 03:58 -0700, Jan Beulich wrote:
> > > > > > On 10.11.15 at 18:59, <osstest-admin@xenproject.org> wrote:
> > > > flight 63948 xen-4.3-testing real [real]
> > > > http://logs.test-lab.xenproject.org/osstest/logs/63948/
> > > >
> > > > Regressions :-(
> > > >
> > > > Tests which did not succeed and are blocking,
> > > > including tests which could not be run:
> > > > test-amd64-amd64-migrupgrade 21 guest-migrate/src_host/dst_host
> > > > fail
> > > > REGR. vs. 63212
> > >
> > > This having failed for quite some time, I've finally looked more
> > > closely
> > > and found
> > >
> > > Nov 10 14:36:16.949051 (XEN) vmce.c:88: PV restore: unsupported MCA
> > > capabilities 0x1000802 for d1:v0 (supported: 0)
> > >
> > > to be the reason for the EPERM here
> > >
> > > xc: error: Couldn't set extended vcpu0 info (1 = Operation not
> > > permitted): Internal error
> > >
> > > Taking apart the value, it is MCG_SER_P | MCG_TES_P (the low 8 bits
> > > get masked out anyway), which is in line with 4.2's GUEST_MCG_CAP.
> > > Hence I would guess that previous successful runs of this test would
> > > have been on Intel systems only; I can't see how this test would ever
> > > succeed on AMD ones.
> >
> > FWIW you can find the history of any given test at a URL like:
> > http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-
> > amd64
> > -migrupgrade/xen-4.3-testing.html
> >
> > Figuring out the arch of the machines is a bit of a faff, especially
> > since
> > some of the relevant logs no longer exist. From
> > http://logs.test-lab.xenproject.org/osstest/results/host/huxelrebe0.htm
> > l
> > http://logs.test-lab.xenproject.org/osstest/results/host/godello0.html
> > http://logs.test-lab.xenproject.org/osstest/results/host/pinot0.html
> >
> > I found recent logs which confirm (via the serial log):
> > Huxelrebe:
> > CPU0: Intel(R) Xeon(R) CPU E3-1225 v3 @ 3.20GHz stepping 03
> > Godello:
> > CPU0: Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz stepping 03
> > Pinot:
> > CPU0: AMD Opteron(tm) Processor 3350 HE stepping 00
> >
> > With Huxelrebe passing and godello and pinot failing this doesn't seem
> > to
> > correlate with your investigation though.
>
> Looking at that history page you point me to, I see passes on
> godello.
Uh, yes, two brainfarts on my part, first in mixing up that result,
secondly in inverting which one I thought you were saying worked vs didn't.
Sorry.
>
> > > Considering that 4.3 is out of maintenance, I
> > > think the only reasonable change to avoid endless failure here is to
> > > limit this test to Intel systems for this version.
> >
> > Aside from the above I don't think osstest is currently aware of the
> > vendor
> > of the processors (although I can certainly think of several reasons it
> > should be).
> >
> > But given this is a new test case I would be happy, I think, to
> > restrict it
> > to only go back as far as the earliest release which was in maintenance
> > at
> > the time the test was introduced (August this year), or maybe (if
> > something
> > just dropped out of maintenance recently) just the ones maintained
> > today
> > (since it took a while for the test case to "bed in" and be made
> > working on
> > some of the older ones). FWIW the last related fix I see in osstest was
> > early October.
>
> That would be fine too.
I'll wait for Ian to have an opinion before doing anything.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-11-11 11:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 17:59 [xen-4.3-testing test] 63948: regressions - FAIL osstest service owner
2015-11-11 10:58 ` Jan Beulich
2015-11-11 11:25 ` Ian Campbell
2015-11-11 11:35 ` Jan Beulich
2015-11-11 11:51 ` Ian Campbell [this message]
2015-11-11 15:30 ` Ian Jackson
2015-11-11 15:34 ` Ian Campbell
2015-11-11 15:58 ` Ian Jackson
2015-11-11 16:17 ` Jan Beulich
2015-11-11 16:21 ` Ian Campbell
2015-11-11 16:54 ` [xen-4.3-testing test] 63948: regressions - FAIL [and 1 more messages] Ian Jackson
2015-11-15 23:19 ` [xen-4.3-testing test] 64287: regressions - FAIL osstest service owner
2015-11-16 16:00 ` [xen-4.3-testing test] 63948: regressions - FAIL [and 1 more messages] [and 1 more messages] Ian Jackson
2015-11-16 16:11 ` Jan Beulich
2015-11-16 16:14 ` Ian Jackson
2015-11-16 16:24 ` Jan Beulich
2015-11-16 16:55 ` 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=1447242703.11601.37.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=osstest-admin@xenproject.org \
--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.