Re: [Qemu-devel] [PATCH] .travis.yml: basic compile and check recipes

["Alex Bennée" <alex.bennee@linaro.org>]

stefanha@gmail.com writes:

> On Wed, Sep 18, 2013 at 03:35:07PM +0100, Alex Bennée wrote:
>> 
>> stefanha@gmail.com writes:
>> 
>> >
>> > Looks useful.  To get more code coverage, flesh out the build
>> > environment:
>> 
>> Thanks. Am I dreaming or are there some system image tests somewhere as well?
>
> Anthony Liguori's "qemu-test" builds special-purpose Linux test guests:
> http://git.qemu-project.org/?p=qemu-test.git;a=tree

It looks like this is more the sort of thing I want. Given the first
thing I found when playing with QEMU was a regression to one of the
system emulations (admittedly not one that's used that often nowadays
but it was the default). 

> <snip>
> Both qemu-test and KVM Autotest are heavy in the sense that they will
> download 100s of MB.  Not sure if they are suitable for Travis CI.

Surely a kernel with minimal user-space and running a simple script can
be kept under 10Mbs? This is essentially a smoke test to ensure QEMU can
still boot a kernel with whatever hardware it's trying to emulate. I'm
not sure the core translator needs much more exercising from user space
after it's booted up? I guess I should do some coverage profiling to
check.

The Travis docs do mention a concept of binary packages of test data but
it's a little unclear if it could be applied to this problem. There is
something about fetching things from Amazon S3. Does the QEMU project
have much in the way of hosting facilities or does it rely on commercial
users to provide them?

I wonder if there is an argument for allowing qemu-test to be added as a
submodule of qemu so the test scripts can be accessed directly even if
the images are pre-canned and stored somewhere else?

Cheers,

-- 
Alex Bennée