Ian Campbell writes ("Re: [PATCH v2] OSSTest: stop testing SEDF, start testing
RTDS"):
> On Tue, 2015-06-30 at 10:11 +0100, Ian Jackson wrote:
> > I hope you are able to set up the appropriate email filter.
>
> Perhaps we could provide some X-osstest-* headers to help? Branch and
> Flight are alr
On Tue, 2015-06-30 at 10:11 +0100, Ian Jackson wrote:
> Meng Xu writes ("Re: [PATCH v2] OSSTest: stop testing SEDF, start testing
> RTDS"):
> > Thank you very much for your explanation!
> >
> > 2015-06-29 2:33 GMT-07:00 Dario Faggioli :
> ...
> > > (the subject changes a bit, depending on the act
Meng Xu writes ("Re: [PATCH v2] OSSTest: stop testing SEDF, start testing
RTDS"):
> Thank you very much for your explanation!
>
> 2015-06-29 2:33 GMT-07:00 Dario Faggioli :
...
> > (the subject changes a bit, depending on the actual tests results, but
> > that's the patter.
>
>
> Yes. I noticed
Hi Ian and Dario,
Thank you very much for your explanation!
2015-06-29 2:33 GMT-07:00 Dario Faggioli :
>
> On Mon, 2015-06-29 at 09:53 +0100, Ian Campbell wrote:
> > On Sat, 2015-06-27 at 12:05 -0700, Meng Xu wrote:
>
> > > I want/hope to know when/how the RTDS scheduler fails the test so that
>
On Mon, 2015-06-29 at 09:53 +0100, Ian Campbell wrote:
> On Sat, 2015-06-27 at 12:05 -0700, Meng Xu wrote:
> > I want/hope to know when/how the RTDS scheduler fails the test so that
> > I can also contribute to fix the issue.
>
> I think other than keeping an eye on the reposts on the reports on
On Sat, 2015-06-27 at 12:05 -0700, Meng Xu wrote:
> Will I receive the email in cc. list if OSSTest fails?
Test reports are in general only sent to xen-devel.
While osstest could in theory cc people who touched the branch with e.g.
a branch which tests Linux that would risk spamming a load of Li
Hi Dario,
A dummy question:
>
> For now, as RTDS is still marked as experimental,
> test failures are allowed, as it is for SEDF.
>
Will I receive the email in cc. list if OSSTest fails?
I want/hope to know when/how the RTDS scheduler fails the test so that
I can also contribute to fix the issu
Dario Faggioli writes ("[PATCH v2] OSSTest: stop testing SEDF, start testing
RTDS"):
> 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 th
On Fri, 2015-06-26 at 12:08 +0100, Ian Campbell wrote:
> On Fri, 2015-06-26 at 12:58 +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
> >
On Fri, 2015-06-26 at 12:58 +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
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; i
11 matches
Mail list logo
