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

2013-10-15 Thread alex . bennee
From: Alex Bennée This adds a build matrix definition for travis-ci.org continuous integration service. It is usable on any public repository hosted on GitHub. Once you have created an account signed into Travis you can enable it on selected projects via travis-ci.org/profile. Alternatively you c

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

2013-09-26 Thread Stefan Hajnoczi
On Wed, Sep 25, 2013 at 11:00:05AM +0100, Alex Bennée wrote: > > peter.mayd...@linaro.org writes: > > > On 25 September 2013 01:31, wrote: > >> +# This disabled make check for the ftrace backend which needs more > >> setting up > >> +# Currently broken on 12.04 due to mis-packaged libu

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

2013-09-25 Thread Alex Bennée
peter.mayd...@linaro.org writes: > On 25 September 2013 01:31, wrote: >> +# Debug related options >> +- env: TARGETS=i386-softmmu,x86_64-softmmu >> + EXTRA_CONFIG="--enable-debug --enable-debug-tcg >> --enable-tcg-interpreter" > > --enable-debug implies --enable-debug-tcg, yo

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

2013-09-24 Thread Peter Maydell
On 25 September 2013 01:31, wrote: > +# Debug related options > +- env: TARGETS=i386-softmmu,x86_64-softmmu > + EXTRA_CONFIG="--enable-debug --enable-debug-tcg > --enable-tcg-interpreter" --enable-debug implies --enable-debug-tcg, you don't need to specify it separately. I th

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

2013-09-24 Thread alex . bennee
From: Alex Bennée This adds a build matrix definition for travis-ci.org continuous integration service. It is usable on any public repository hosted on GitHub. Once you have created an account signed into Travis you can enable it on selected projects via travis-ci.org/profile. Alternatively you c

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

2013-09-19 Thread Alex Bennée
stefa...@gmail.com writes: > On Wed, Sep 18, 2013 at 03:35:07PM +0100, Alex Bennée wrote: >> >> stefa...@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

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

2013-09-19 Thread Stefan Hajnoczi
On Thu, Sep 19, 2013 at 6:01 PM, Alex Bennée wrote: > > stefa...@gmail.com writes: > >> On Wed, Sep 18, 2013 at 03:35:07PM +0100, Alex Bennée wrote: >>> >>> stefa...@gmail.com writes: >>> >>> > >>> > Looks useful. To get more code coverage, flesh out the build >>> > environment: >>> >>> Thanks. A

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

2013-09-19 Thread Stefan Hajnoczi
On Wed, Sep 18, 2013 at 03:35:07PM +0100, Alex Bennée wrote: > > stefa...@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" bu

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

2013-09-18 Thread Alex Bennée
stefa...@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? -- Alex Bennée

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

2013-09-18 Thread Stefan Hajnoczi
On Fri, Sep 13, 2013 at 04:20:22PM +0100, alex.ben...@linaro.org wrote: > From: Alex Bennée > > While QEMU already has various continuous integration set-ups in > buildbot and commercial Jenkins setups there is some value in supporting > travis-ci as well. It is well integrated into GitHub work f

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

2013-09-13 Thread alex . bennee
From: Alex Bennée While QEMU already has various continuous integration set-ups in buildbot and commercial Jenkins setups there is some value in supporting travis-ci as well. It is well integrated into GitHub work flow and will trigger on all branch pushes and pull requests. This makes it easier