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

[Meng Xu <xumengpanda@xxxxxxxxx>]

Hi Dario,

2015-05-22 3:19 GMT-07:00 Dario Faggioli <dario.faggioli@xxxxxxxxxx>:
>
> [ Adding to Cc the people that I though I added when sending the patch,
>   but that apparently I haven't...sorry :-( ]

Thanks for cc.ing us. :-)

>
> 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.
> >
> > It therefore makes sense to stop smoke testing the
> > former in favour of the latter. Note that the
> > -sedf-pin jobs where only added in order to try to
> > debug a long standing issue with SEDF; it is not
> > necessary to have anything like that for RTDS.
> >
> > For now, as RTDS is still marked as experimental,
> > test failures are allowed, as it was for SEDF.
> >
> > [1] http://lists.xen.org/archives/html/xen-devel/2015-05/msg02874.html
> >
> Oh, and here's the diff of the generated runvars that IanJ usually asks
> about: :-)

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?

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.
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?)

Thanks,

Meng

-----------
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/

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