qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: kwolf@redhat.com, peter.maydell@linaro.org, jsnow@redhat.com,
	qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [RFC PATCH 0/4] tests: Introducing docker tests
Date: Wed, 3 Feb 2016 15:24:25 +0000	[thread overview]
Message-ID: <20160203152425.GA9435@stefanha-x1.localdomain> (raw)
In-Reply-To: <1454510164-6278-1-git-send-email-famz@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]

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.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  parent reply	other threads:[~2016-02-03 15:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 14:36 [Qemu-devel] [RFC PATCH 0/4] tests: Introducing docker tests Fam Zheng
2016-02-03 14:36 ` [Qemu-devel] [RFC PATCH 1/4] tests: Introduce Docker based tests Fam Zheng
2016-02-04 11:58   ` Daniel P. Berrange
2016-02-05  6:17     ` Fam Zheng
2016-02-03 14:36 ` [Qemu-devel] [RFC PATCH 2/4] tests: Add clang docker test Fam Zheng
2016-02-03 14:36 ` [Qemu-devel] [RFC PATCH 3/4] tests: Add mingw 32/64 cross compiling Fam Zheng
2016-02-03 15:08   ` Stefan Weil
2016-02-04  2:29     ` Fam Zheng
2016-02-04 11:24       ` Paolo Bonzini
2016-02-03 16:14   ` Eric Blake
2016-02-04  2:28     ` Fam Zheng
2016-02-04 12:00   ` Daniel P. Berrange
2016-02-03 14:36 ` [Qemu-devel] [RFC PATCH 4/4] tests: Add travis container test case Fam Zheng
2016-02-03 15:24 ` Stefan Hajnoczi [this message]
2016-02-04  2:43   ` [Qemu-devel] [RFC PATCH 0/4] tests: Introducing docker tests Fam Zheng
2016-02-04 11:26     ` Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160203152425.GA9435@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=famz@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).