[oe] why we don't setup a buildbot for openembedded QA?

[Guo Hongruan]

在 Wed, 06 Jan 2010 11:59:45 +0800，Holger Hans Peter Freyther  
<holger+oe at freyther.de> 写道:

> On Tuesday 05 January 2010 03:06:47 Guo Hongruan wrote:
>> No, I am not talking about tinderbox but buildbot. I want to setup a
>> public buildbot and validate every possible combinations of  
>> openembedded.
>> In another words, I want to do some QA jobs of openembedded.
>
> This is a nice goal, but it is probably not the biggest concern as well.  
> E.g.
> there is little benefit of making every version of binutils work with  
> glibc and
> gcc. It is certainly cool to be able to pick any GCC, BINUTILS, GLIBC and
> guarnatee that it will work on any host distro. But besides being  
> totally cool
> it is also totally wasting your time (unless your goal is to learn how  
> GCC,
> BINUTILS and GLIBC interact). And the next step would be to have make  
> world
> build on top of that...

Yes, I agree with you. It is not worth to make sure every combinations of  
GCC, GLIBC and BINUTILS work perfectly. For example, some versions of  
binutils is too old to work with newest glibc/gcc and there are little  
projects using these combinations.

But, My idea is that we can maintain a table which records which version  
of package A can not work with which version of package B.
(for example, glibc-2.6.1 can not work with binutils-2.20)
So that, when the user chooses these combinations, the  
openembedded/bitbake can give them a warning or error to indicate that  
this combination will not work.

>
>
> I have been at your point a couple of years back (seppuku, a tinderbox  
> setup,
> autobuild scripts are the result). The QA that is working best is to have
> people sign up for "maintaining" certain areas.
>
> E.g.: I'm feeling responsible for:
>
> 	- QtE, meta-toolchain-qte, qmake and such
> 	- I'm also testing mipsel from time to time
>
> Other people like pb_ feel responsible for:
> 	- DISTRO micro (I think i got it wrong)
>
> Or Khem is doing kick ass work on the toolchain bits..
>
>
>> Of course, I need help and support from all of you. I want a public  
>> server
>> which runs python and twist and I also want any volunteer can provide
>> their machine as build slaver when it is available.
>
> Technology is not the problem here. What use is this system if no one is  
> fixing
> build problems because of a too new or too old version of GCC? What use  
> is it
> to the user to have thousands of tested configurations when he can not  
> navigate
> through the list of packages?
>
>
> let me write another mail about QA topics.
>
> 	z.
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


-- 
Guo Hongruan, Embedded Linux Consultant
Skype: camelguo
Twitter: camelguo
http://www.gulessoft.com