From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: QA Goals for OpenEmbedded
Date: Wed, 06 Jan 2010 09:17:52 +0100 [thread overview]
Message-ID: <hi1gvg$auc$1@ger.gmane.org> (raw)
In-Reply-To: <201001060507.31754.holger+oe@freyther.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 06-01-10 05:07, Holger Hans Peter Freyther wrote:
>
> *) 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?
>
> *) The next step would be to transfer packet sizes as well
>
> *) Integrate some testing into recipes. E.g. attempt to boot the console-
> image and grep the Serial Console for the "Loging:" prompt..
> Test the toolchain to compile binaries...
Those 3 points are exactly what testlab.bbclass was created for :) Over
2 years old now, but illustrates the usefullness of that class:
http://dominion.thruhere.net/koen/cms/the-testlab-strikes-again
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLREcwMkyGM64RGpERAquMAJ0ew07LQRZutS5gu6vCIvmyukEEAgCeJ6Lx
/4mvjNmmqeVP6TbVl8pRSYY=
=qUTY
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-01-06 8:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 4:07 QA Goals for OpenEmbedded Holger Hans Peter Freyther
2010-01-06 7:49 ` Frans Meulenbroeks
2010-01-06 8:17 ` Koen Kooi [this message]
2010-01-06 15:26 ` Richard Purdie
2010-01-06 15:55 ` Martin Jansa
2010-01-06 22:09 ` Rolf Leggewie
2010-01-06 22:57 ` Philip Balister
2010-01-07 2:36 ` Holger Hans Peter Freyther
2010-01-07 7:59 ` Frans Meulenbroeks
2010-01-07 8:43 ` Graeme Gregory
2010-01-07 8:50 ` Frans Meulenbroeks
2010-01-07 9:21 ` Graeme Gregory
2010-01-07 9:35 ` Frans Meulenbroeks
2010-01-07 9:40 ` Koen Kooi
2010-01-07 9:54 ` Frans Meulenbroeks
2010-01-07 10:40 ` Rolf Leggewie
2010-01-07 11:01 ` Graeme Gregory
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='hi1gvg$auc$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.