On Thu, Sep 23, 2010 at 08:18:06AM +1200, Michael Hope wrote: > >> I had been thinking about this as well, would you see more benefit for this > >> to focus on testing the latest image, or qemu itself? > > > > I think the image (and the kernel) are going to churn at a much faster > > rate than qemu will, so the benefit really is in early warning if the > > kernel has suddenly tickled a latent qemu bug/missing bit of model. > > (ie I think we'd want to do this test with the latest released qemu-maemo > > package as well as with any new daily build of qemu.) > > To overdo things, it would be nice to mix the compiler in as well. > I've been planning to add a test case to the compiler build that > builds the current Ubuntu kernel and boots it inside QEMU.
Let's just test the image. The toolchain and qemu will be tested as a side-effect, but let's not lessen the benefit of ensuring our image runs on a "released" qemu. -- Christian Robottom Reis | [+55 16] 3376 0125 | http://launchpad.net/~kiko Canonical Ltd. | [+55 16] 9112 6430 | http://async.com.br/~kiko _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
