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
Subject: Re: [xen-unstable test] 56811: regressions - FAIL
Date: Thu, 21 May 2015 09:45:35 +0100 [thread overview]
Message-ID: <1432197935.10746.9.camel@citrix.com> (raw)
In-Reply-To: <555D9AB8020000780007C8AF@mail.emea.novell.com>
On Thu, 2015-05-21 at 07:43 +0100, Jan Beulich wrote:
> >>> On 21.05.15 at 05:34, <osstest@xenbits.xen.org> wrote:
> > flight 56811 xen-unstable real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/56811/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> > test-armhf-armhf-xl-multivcpu 17 leak-check/check fail REGR. vs. 56375
>
> Anyone having an idea about this one?
I posted <1432115769.12989.219.camel@citrix.com> in reply to "56759:
regressions - FAIL".
The only thing in that range which is even vaguely plausibly related
(IMHO) is the spinlock thing but why it is not just ARM specific but
multivcpu specific _and_ somehow affecting xenstore or hotplug scripts I
cannot fathom...
The bisector is still working on it at
http://logs.test-lab.xenproject.org/osstest/results/bisect.xen-unstable.test-armhf-armhf-xl-multivcpu.leak-check--check.html although I'm not sure if it is actually going to produce a result.
Ian.
next prev parent reply other threads:[~2015-05-21 8:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 3:34 [xen-unstable test] 56811: regressions - FAIL osstest service user
2015-05-21 6:43 ` Jan Beulich
2015-05-21 8:45 ` Ian Campbell [this message]
2015-05-22 14:41 ` 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=1432197935.10746.9.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.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.