From: "Alex Bennée" <alex.bennee@linaro.org>
To: Fam Zheng <famz@redhat.com>
Cc: kwolf@redhat.com, peter.maydell@linaro.org, sw@weilnetz.de,
qemu-devel@nongnu.org, stefanha@redhat.com,
Paolo Bonzini <pbonzini@redhat.com>,
jsnow@redhat.com, david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [PATCH v4 02/13] Makefile: Rules for docker testing
Date: Thu, 31 Mar 2016 11:32:41 +0100 [thread overview]
Message-ID: <8760w3gcom.fsf@linaro.org> (raw)
In-Reply-To: <1458196505-5473-3-git-send-email-famz@redhat.com>
Fam Zheng <famz@redhat.com> writes:
> This adds a group of make targets to run docker tests, all are available
> in source tree without running ./configure.
>
> The usage is shown with "make docker".
>
> Besides the fixed ones, dynamic targets for building each image and
> running each test in each image are generated automatically by make,
> scanning $(SRC_PATH)/tests/docker/ files with specific patterns.
>
> Alternative to manually list particular targets (docker-TEST@IMAGE)
> set, you can control which tests/images to run by filtering variables,
> TESTS= and IMAGES=, which are expressed in Makefile pattern syntax,
> "foo% %bar ...". For example:
>
> $ make docker-test IMAGES="ubuntu fedora"
>
> Unfortunately, it's impossible to propagate "-j $JOBS" into make in
> containers, however since each combination is made a first class target
> in the top Makefile, "make -j$N docker-test" still parallels the tests
> coarsely.
>
> Still, $J is made a magic variable to let all make invocations in
> containers to use -j$J.
>
> Instead of providing a live version of the source tree to the docker
> container we snapshot it with git-archive. This ensures the tree is in a
> pristine state for whatever operations the container is going to run on
> them.
>
> Uncommitted changes known to files known by the git index will be
> included in the snapshot if there are any.
>
> Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> Makefile | 4 +-
> tests/docker/Makefile.include | 121 ++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 124 insertions(+), 1 deletion(-)
> create mode 100644 tests/docker/Makefile.include
>
<snip>
> diff --git a/tests/docker/Makefile.include b/tests/docker/Makefile.include
> new file mode 100644
> index 0000000..033809a
> --- /dev/null
> +++ b/tests/docker/Makefile.include
> @@ -0,0 +1,121 @@
> +# Makefile for Docker tests
<snip>
> +docker-run-%: CMD = $(shell echo '$@' | sed -e 's/docker-run-\([^@]*\)@\(.*\)/\1/')
> +docker-run-%: IMAGE = $(shell echo '$@' | sed -e 's/docker-run-\([^@]*\)@\(.*\)/\2/')
> +docker-run-%: docker-qemu-src
> + @if test -z "$(IMAGE)" || test -z "$(CMD)"; \
> + then echo "Invalid target"; exit 1; \
> + fi
> + $(if $(filter $(TESTS),$(CMD)),$(if $(filter $(IMAGES),$(IMAGE)), \
> + $(call quiet-command,\
> + $(SRC_PATH)/tests/docker/docker.py run $(if $V,,--rm) \
> + --privileged -t \
I had to drop --privileged to get it to work.
> + $(if $(DEBUG),-i,--net=none) \
> + -e TARGET_LIST=$(TARGET_LIST) \
> + -e V=$V -e J=$J -e DEBUG=$(DEBUG)\
> + -e CCACHE_DIR=/var/tmp/ccache \
> + -v $$(realpath $(SRC_COPY)):/var/tmp/qemu:ro \
> + -v $(DOCKER_CCACHE_DIR):/var/tmp/ccache \
> + -w /var/tmp/qemu \
> + qemu:$(IMAGE) \
> + $(if $V,/bin/bash -x ,) \
> + ./run \
> + $(CMD); \
> + , " RUN $(CMD) in $(IMAGE)")))
> +
> +docker-clean:
> + $(call quiet-command, $(SRC_PATH)/tests/docker/docker.py clean)
--
Alex Bennée
next prev parent reply other threads:[~2016-03-31 10:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 6:34 [Qemu-devel] [PATCH v4 00/13] tests: Introducing docker tests Fam Zheng
2016-03-17 6:34 ` [Qemu-devel] [PATCH v4 01/13] tests: Add utilities for docker testing Fam Zheng
2016-03-31 9:47 ` Alex Bennée
2016-03-17 6:34 ` [Qemu-devel] [PATCH v4 02/13] Makefile: Rules " Fam Zheng
2016-03-31 9:52 ` Alex Bennée
2016-03-31 10:32 ` Alex Bennée [this message]
2016-03-17 6:34 ` [Qemu-devel] [PATCH v4 03/13] docker: Add images Fam Zheng
2016-03-17 6:34 ` [Qemu-devel] [PATCH v4 04/13] docker: Add test runner Fam Zheng
2016-03-17 6:34 ` [Qemu-devel] [PATCH v4 05/13] docker: Add common.rc Fam Zheng
2016-03-17 6:34 ` [Qemu-devel] [PATCH v4 06/13] docker: Add quick test Fam Zheng
2016-03-17 6:34 ` [Qemu-devel] [PATCH v4 07/13] docker: Add full test Fam Zheng
2016-03-31 13:26 ` Alex Bennée
2016-03-17 6:35 ` [Qemu-devel] [PATCH v4 08/13] docker: Add clang test Fam Zheng
2016-03-31 13:29 ` Alex Bennée
2016-03-17 6:35 ` [Qemu-devel] [PATCH v4 09/13] docker: Add mingw test Fam Zheng
2016-03-17 6:35 ` [Qemu-devel] [PATCH v4 10/13] docker: Add travis tool Fam Zheng
2016-03-31 13:14 ` Alex Bennée
2016-03-17 6:35 ` [Qemu-devel] [PATCH v4 11/13] docs: Add text for tests/docker in build-system.txt Fam Zheng
2016-03-17 6:35 ` [Qemu-devel] [PATCH v4 12/13] docker: Add EXTRA_CONFIGURE_OPTS Fam Zheng
2016-03-31 13:20 ` Alex Bennée
2016-03-17 6:35 ` [Qemu-devel] [PATCH v4 13/13] MAINTAINERS: Add tests/docker Fam Zheng
2016-03-28 2:37 ` [Qemu-devel] [PATCH v4 00/13] tests: Introducing docker tests Fam Zheng
2016-03-28 11:50 ` Alex Bennée
2016-05-03 8:20 ` Alex Bennée
2016-05-03 9:36 ` Fam Zheng
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=8760w3gcom.fsf@linaro.org \
--to=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 \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.de \
/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).