[Kerncomp-devel] Re: [ANNOUNCE] Automated Kernel Build Regression Testing

[Jan D. <jdi...@pp...>]

Ian Wienand wrote:
>>By grabbing the patches from kernel.org, I've definite checkpoints
>>what was tested and you can fully rebuilt the build environment
>>locally. For grabbing the different trees I use a tool called
>>'ketchup'.
> 
> 
> Good point.  BK used to make it really easy to update your tree with
> what was pulled from the logs; we will see how this works out with
> Cogito.

You should at least log the current .git/HEAD when building, to reproduce
the tree afterwards.

>>ls arch/*/configs/* gives about 184 different defconfigs. A test run
>>on my single workstation would take literally ages. Therefore I'd
>>consider a distributed client/server approach.
> 
> 
> For a broad approach like your cross compilers; for sure.  For other
> architectures testing those defconfigs can give you pretty much
> complete coverage.  

You know about ARMLinux Kautobuild? [1] That's also pretty far
developed and does _lots_ of configs. Though arm is somewhat quicker
to build than ia64.

>>I though about doing runtime testing with qemu or by using a network
>>of different arch machines. But at home I only have i386 and sparc32
>>so I considered it rather pointless. And qemu is also not that stable
>>that I'd trust the results.
> 
> 
> Luckily IA64 has the ski simulator which, on the whole, is really
> good.  You are right; anything is possible with a bunch of machines!

What are the goals any of this kerncomp project anyways? Just collecting
resources or were you planning on developing _the_ kernel compile and
runtime test application or just not really decided yet?

>>Same are mine. And currently very focussed on kernel building. I'd have
>>to look over them, and then I could post them if you're interested.
> 
> 
> I would be happy to give you a CVS tree in our SF project if you are
> thinking of releasing your code.  That way at least resources are
> together.

Yes, I consider that, but I've to do at least a bit clean up before.
Currently the code state is just too embarassing.

[1] http://armlinux.simtec.co.uk/kautobuild/

-- 
Jan