Re: [Xen-devel] [PATCH] Osstest: stop testing SEDF, start testing RTDS

[Dario Faggioli <dario.faggioli@xxxxxxxxxx>]

On Fri, 2015-05-22 at 21:29 -0700, Meng Xu wrote:
> Hi Dario,
> 
Hi,

> 2015-05-22 3:19 GMT-07:00 Dario Faggioli <dario.faggioli@xxxxxxxxxx>:

> >
> > On Fri, 2015-05-22 at 11:55 +0200, Dario Faggioli wrote:
> > > the SEDF scheduler is about to be deprecated and go
> > > away (see [1]). OTOH, the RTDS scheduler is here to
> > > stay.
> > >

> I'm not so familiar with osstest. (Maybe I should have a look at it so
> that we can know how to use it for some auto tests.)
> I just have a quick (probably dummy) question:
> Do we have any document that describes the coverage of the test?
> 
If, by document, you mean the documentation one would need to used
OSSTest, do development on it, and maybe setup and run an instance of,
there is some docs --certainly much more than even a few weeks before
now:

README files in the sources}
https://blog.xenproject.org/2013/02/02/xen-automatic-test-system-osstest/
http://www.xenproject.org/component/allvideoshare/video/xpds13-osstest.html
https://blog.xenproject.org/2013/09/30/osstest-standalone-mode-step-by-step/

Setting up your own instance would be rather tricky, though, at least
untile you get used enough to it.

> The reason I asked this
> is:
> 1) The document could make it easier for users to know which
> functionalities of the feature (i.e., RTDS scheduler here) have been
> tested.
>
I don't think that's how OSSTest works or how it should be used. OSSTest
is meant for us developers, in order to be sure that we do not cause
regressions. That's why it gates commits.

Users, if we say (e.g., in some release notes), that a feature is
'ready'/\supported\/whatever should be able to use it fully, and
complain if it doesn't work, regardless of what tests us developers or
OSSTest have run!

> 2) I didn't see the toolstack functionality of RTDS scheduler is
> called in the test. So I'm wondering about the first question. :-)
> (probably I missed something?)
> 
The test does what it's being done already for other schedulers: sets
RTDS as the default scheduler, boots Xen with it, then it creates a
domain, and it starts and stop it a few times.

If you want to have a look, check make-flight, sg-run-job,
ts-guest-start and ts-guest-stop in OSSTest's codebase.

We do not do any testing of changing scheduling parameters of a guest,
if that was what you were referring to, for any of the schedulers. We of
course can introduce that (and do it for everyone), but that would be
another patch series.

Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel