On Fri, 2011-06-17 at 11:13 +0100, Phil Blundell wrote: > On Thu, 2011-06-16 at 16:18 -0700, Khem Raj wrote: > > On 06/16/2011 07:29 AM, Phil Blundell wrote: > > > On Thu, 2011-06-16 at 06:41 -0700, Khem Raj wrote: > > >> I nfsmount eglibc builddir on target and run the testsuite. I see aroung > > >> 10-15 fails. Havent run the testsuite in a while > > > > > > Maybe the right thing to do with eglibc would be to build a rootfs > > > containing the testsuite, run it up in qemu-system-arm, and then > > > engineer some IPC mechanism to get the test results back to the host. > > > > using nfs isnt bad either since the tests excercise libraries from /lib > > on target IOW installed eglibc. > > True, though I can't think of any instances where the libc behaviour > will change depending on where it's installed. > > The thing about nfs is that it's awkward to set up in an automated way.
The qemu scripts in OE-Core use usermode NFS by default for booting qemu images... > What I want is to arrive at a situation where you can just do: > > $ bitbake -c check micro-base-image (or whatever) > > and have it build all the necessary components, run their respective > testsuites, and generate a report of both the current status and any > regressions. Ideally I want this to be doable without a lot of > installation-specific fiddling around with networking configuration and > suchlike, and I definitely want an arrangement which doesn't rely on > having target hardware on hand. Practically speaking I think that means > it basically has to be qemu of some kind or another. > > > Yes I think I should put together my mechanism somewhere and post it > > and dejaGNU setup I use for cross testing > > That would be cool. We have the automated image QA tests in OE-Core already so perhaps we could extend these to handle the tests somehow? Cheers, Richard _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
