From: Dario Faggioli <raistlin@linux.it>
To: "xen.org" <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [xen-unstable test] 11901: tolerable FAIL - PUSHED
Date: Thu, 09 Feb 2012 08:30:08 +0100 [thread overview]
Message-ID: <1328772608.4351.55.camel@Abyss> (raw)
In-Reply-To: <osstest-11901-mainreport@xen.org>
[-- Attachment #1.1: Type: text/plain, Size: 1096 bytes --]
On Wed, 2012-02-08 at 19:34 +0000, xen.org wrote:
> flight 11901 xen-unstable real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/11901/
>
> Failures :-/ but no regressions.
>
> Regressions which are regarded as allowable (not blocking):
> test-amd64-amd64-xl-sedf-pin 13 guest-localmigrate.2 fail REGR. vs. 11896
>
Mmm... Avoiding "all vcpus are guaranteed 75% of a *single* pcpu" in
SEDF made things better, as I haven't seen a boot failure since.
However, both this (pinned) and the other test case, sometimes report
this local migration issue. I wonder if there is something else,
unrelated to the previous problem, maybe specific to migration...
I can't look at it right away, but I'll try to schedule some time for
investigating. Any comments/ideas are welcome. :-)
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-------------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2012-02-09 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 19:34 [xen-unstable test] 11901: tolerable FAIL - PUSHED xen.org
2012-02-09 7:30 ` Dario Faggioli [this message]
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=1328772608.4351.55.camel@Abyss \
--to=raistlin@linux.it \
--cc=ian.jackson@eu.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.