[Ksummit-discuss] [CORE TOPIC] kernel testing standard

Masami Hiramatsu masami.hiramatsu.pt at hitachi.com
Fri Jun 6 09:17:40 UTC 2014


(2014/06/05 23:10), James Bottomley wrote:
> On Thu, 2014-06-05 at 10:30 +0200, Geert Uytterhoeven wrote:
>> On Thu, Jun 5, 2014 at 8:54 AM, Mel Gorman <mgorman at suse.de> wrote:
>>> There is a hazard that someone bisecting the tree would need to be careful
>>> to not bisect LTP instead.
>>
>> That may actually be a good reason not to import LTP...
>> I'd imagine you usually want to bisect the kernel to find when a regression
>> was introduced in the syscall API.
> 
> I agree with this.  One of the things we might like to ask to be fixed
> about bisect is the ability to exclude paths.  You can do a git bisect
> with every top level directory except test, but it's a bit cumbersome.
> 
>> Is there a reason not to run the latest version of LTP (unless bisecting
>> LTP ;-)? The syscall API is supposed to be stable.
> 
> I think not, and we have strong reasons for wanting to run the latest
> LTP against every kernel (including stable ones), not just the version
> in the test directory, so in practise, it looks like this doesn't meet
> the changes with the kernel test for inclusion.  On the other hand,
> having the tests available is also useful.   Perhaps we just need a
> tests repo which pulls from all our other disparate tests so there's one
> location everyone knows to go for the latest?

I agree. I guess that may be a script of chef or something like, which
pulls tests from other repos and build it. But in that case, why can't we
put it in the kernel tree itself?

Thank you,

-- 
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt at hitachi.com




More information about the Ksummit-discuss mailing list