[oe] QA Goals for OpenEmbedded

Martin Jansa martin.jansa at gmail.com
Wed Jan 6 15:55:29 UTC 2010


On Wed, Jan 06, 2010 at 03:26:41PM +0000, Richard Purdie wrote:
> On Wed, 2010-01-06 at 05:07 +0100, Holger Hans Peter Freyther wrote:
> > 	*) Koen reported that dependency loop reporting is not working anymore..
> >             anyone cares to invest thes five minutes to fix that?
> 
> In bitbake?

I've seen that too on the same case as Koen, for me it didn't fail
visibly, but after saying that it runs dependency loop detection it
hanged for about 20 mins still working.. then I killed it...

Dependency loop between bitbake tasks was resolved ok and fast (last
time I was changing do_deploy position in kernel.bbclass).

> > 	*) Sometimes we have pretty embarassing issues like some images switching
> >             from mdev back to udev and we don't notice for months(!!!)
> >             It would totally rock if one could change the rootfs.bbclass (or
> >             such) class and count the size of the image on the first run, store 
> >             it in the temp directory and report the diff's back to the 
> >             tinderbox and then we could have a view on the tinderbox?
> > 
> >             Inside the build summary we should see the new size of the image
> >             and the growth compared to the first built?
> > 
> >             The idea would be to have people look at the waterfall and go OMG 
> >             why did "minimal-image" grow by 2MB?
> 
> I started packagehistory.bbclass in Poky with ideas like this in mind.
> It stores data in a filesystem layout and checked package versions don't
> go backwards. Adding transports to send and receive data from a database
> server would be a nice improvement.
> 
> >           *) The next step would be to transfer packet sizes as well
> 
> package sizes? Again this was a goal for packagehistory.bbclass

Maybe not as much QA as above examples, but would be nice to add .md5
sums not only to downloaded sources but also to generated files in
deploy dir (feeds are safe but images are created without).

I've checked kernel.bbclass and image.bbclass and it seems quite easy to
implement, should I prepare patch for that or is there something already?

Cheers,

-- 
uin:136542059                jid:Martin.Jansa at gmail.com
Jansa Martin                 sip:jamasip at voip.wengo.fr 
JaMa                         




More information about the Openembedded-devel mailing list