From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xensource.com, Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [xen-unstable test] 59040: regressions - FAIL
Date: Mon, 6 Jul 2015 14:37:31 +0100 [thread overview]
Message-ID: <1436189851.25646.86.camel@citrix.com> (raw)
In-Reply-To: <20150706132321.GA1134@zion.uk.xensource.com>
On Mon, 2015-07-06 at 14:23 +0100, Wei Liu wrote:
> I saw this bug since the introduction of amd64-i386 stubdom test case.
> Now it looks like intermittent, i.e. we failed at the beginning, passed
> at some point, now it failed again.
http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm/xen-unstable.html
gives the history of it.
It looks as if italia* and chardonnay* might be susceptible but really I
don't think there is sufficient information to draw any particular
conclusion wrt the frequency of this bug or whether it might be host
specific or not, since the passes on other hosts are general singletons.
The 64-bit dom0 case is at
http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm/xen-unstable.html
I'm not sure what, if anything, it tells us though. It does look to be
more less prone to errors (it having now hit merlot notwithstanding,
although it seems to reliably pass the install phase there).
One potentially interesting case is that in the 32-bit dom0 case the
stubdom is also 32-bit, while in the other case the stubdom is 64-bit.
I'm not convinced using a 32-bit stubdom is the right choice, but I
suppose it ought to work.
Ian.
next prev parent reply other threads:[~2015-07-06 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 21:59 [xen-unstable test] 59040: regressions - FAIL osstest service owner
2015-07-06 12:33 ` Ian Campbell
2015-07-06 12:47 ` Ian Jackson
2015-07-06 12:57 ` Ian Campbell
2015-07-06 13:23 ` Wei Liu
2015-07-06 13:37 ` Ian Campbell [this message]
2015-07-06 13:52 ` Wei Liu
2015-07-06 14:05 ` Dario Faggioli
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=1436189851.25646.86.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--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.