From: Dario Faggioli <raistlin@linux.it>
To: Jan Beulich <JBeulich@suse.com>
Cc: keir@xen.org, xen-devel <xen-devel@lists.xen.org>,
ian.jackson@eu.citrix.com, stefano.stabellini@eu.citrix.com
Subject: Re: [xen-unstable bisection] complete test-amd64-amd64-xl-win7-amd64
Date: Wed, 20 Jun 2012 19:18:11 +0200 [thread overview]
Message-ID: <1340212691.20225.19.camel@Solace> (raw)
In-Reply-To: <4FE19D1B020000780008ABDB@nat28.tlf.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 2090 bytes --]
On Wed, 2012-06-20 at 08:51 +0100, Jan Beulich wrote:
> >>> On 20.06.12 at 04:40, xen.org <ian.jackson@eu.citrix.com> wrote:
> > branch xen-unstable
> > xen branch xen-unstable
> > job test-amd64-amd64-xl-win7-amd64
> > test windows-install
> >
> > Tree: linux git://xenbits.xen.org/linux-pvops.git
> > Tree: qemu git://xenbits.xen.org/staging/qemu-xen-unstable.git
> > Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git
> > Tree: xen http://xenbits.xen.org/staging/xen-unstable.hg
> >
> > *** Found and reproduced problem changeset ***
> >
> > Bug is in tree: xen http://xenbits.xen.org/staging/xen-unstable.hg
> > Bug introduced: 9d1fd58ff602
> > Bug not present: 32034d1914a6
> >
> >
> > changeset: 25468:9d1fd58ff602
> > user: Dario Faggioli <dario.faggioli@citrix.com>
> > date: Fri Jun 08 15:26:01 2012 +0100
> >
> > xl: check for meaningful combination of sedf config file parameters
>
Ok, this was causing a bug at least in *-sedf-* related tes runs, for
which I just sent a fix (<cbd6b5a7d0451a98a8c6.1340212196@Solace>,
[PATCH] xl: fix sedf parameters checking).
Basically, when not specifying explicitly the sedf scheduling
parameters, one couldn't even start a new domain.
I'd swear I tested that case, even more than once, but I apparently am
wrong. :-(
Anyway, sorry for both that and not noticing this sooner. As soon as
we'll have the fix committed (provided you like it) we can see what
happens to both the -sedf and non -sedf runs in future flights. I know
the bisector is something to be trusted, but I really hope to see the
issue for non -sedf cases to be caused by something else, as I can't
reproduce it and neither I can see how that could happen. :-O
Thanks and Regards,
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: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2012-06-20 17:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 2:40 [xen-unstable bisection] complete test-amd64-amd64-xl-win7-amd64 xen.org
2012-06-20 7:51 ` Jan Beulich
2012-06-20 9:06 ` Ian Campbell
2012-06-20 10:34 ` Dario Faggioli
2012-06-20 13:43 ` Ian Jackson
2012-06-20 14:01 ` Dario Faggioli
2012-06-20 15:32 ` Ian Jackson
2012-06-20 17:12 ` Dario Faggioli
2012-06-20 17:18 ` 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=1340212691.20225.19.camel@Solace \
--to=raistlin@linux.it \
--cc=JBeulich@suse.com \
--cc=ian.jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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.