Re: [Qemu-devel] [RFC PATCH 0/4] tests: Introducing docker tests

[Fam Zheng <famz@redhat.com>]

On Wed, 02/03 15:24, Stefan Hajnoczi wrote:
> On Wed, Feb 03, 2016 at 10:36:00PM +0800, Fam Zheng wrote:
> > This series adds a new "docker" make target family to run tests in created
> > docker containers.
> > 
> > To begin with, this can be a place to store standard env/command combinations to
> > build and test QEMU.
> > 
> > Secondly, CI usually provides "docker" capability (such as travis [1]), where
> > we define standard/repeatable test environments, and run tests in them.
> > However, what tests to cover is better maintained in-tree, in order to keep in
> > sync with the code development.
> > 
> > Lastly, this makes it very simple for developers to replicate such tests
> > themselves.
> > 
> > [1]: https://docs.travis-ci.com/user/docker/
> > 
> > 
> > Fam Zheng (4):
> >   tests: Introduce Docker based tests
> >   tests: Add clang docker test
> >   tests: Add mingw 32/64 cross compiling
> >   tests: Add travis container test case
> 
> Nice, having standard build/test environments will make it easier to
> reproduce issues.
> 
> I sent several pull requests to Peter Maydell last year that ended up
> failing in his build environments.  Although some of those issues were
> non-Linux and therefore not captured by your Docker environments,
> capturing common Linux environments is a step forward.

Non-Linux environments can be sorted out in this framework by pulling
appropriate 3rd party images from docker hub, assuming there isn't too much
copyright hassle for Mac OSX and Windows stuff. This is theoretically possible
because with "--privileged -v /dev/kvm:/dev/kvm": we can spawn a kvm guest
inside the container.  Even without kvm, TCG may also be useful for non-x86
build env.

This series also covers mingw cross compiling which might catch some windows
problems. I'm not sure how different is it from natively building QEMU on
Windows with MinGW. Stefan Weil?

Fam