From: Fam Zheng <famz@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 6/6] tests/docker/Makefile.include: expand docker help text
Date: Mon, 31 Oct 2016 10:34:23 +0800 [thread overview]
Message-ID: <20161031023423.GI30303@lemon> (raw)
In-Reply-To: <20161028163339.31096-7-alex.bennee@linaro.org>
On Fri, 10/28 17:33, Alex Bennée wrote:
> No we can query what has and hasn't been built we can make this list
> available in the help text. This is useful as some of the bootstrapped
> builds can take some time to build.
I'm not sure how useful it is to list built images without checking if it's in
sync with the dockerfile: we still rebuild outdated ones even they're built.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> tests/docker/Makefile.include | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/tests/docker/Makefile.include b/tests/docker/Makefile.include
> index bb9e078..a19991b 100644
> --- a/tests/docker/Makefile.include
> +++ b/tests/docker/Makefile.include
> @@ -80,6 +80,10 @@ docker-image-debian-%: $(DOCKER_FILES_DIR)/debian-bootstrap.docker
> --include-executable=$(QEMU_EXEC),\
> "BUILD USER","$*")
>
> +DOCKER_USER_IMAGES := debian-stable-armhf debian-stable-arm64
> +DOCKER_BUILT_IMAGES := $(shell $(SRC_PATH)/tests/docker/docker.py images --repo qemu)
> +DOCKER_UNBUILT_IMAGES := $(filter-out debian-bootstrap, $(filter-out $(DOCKER_BUILT_IMAGES), $(DOCKER_USER_IMAGES) $(DOCKER_IMAGES)))
> +
> docker:
> @echo 'Build QEMU and run tests inside Docker containers'
> @echo
> @@ -96,8 +100,11 @@ docker:
> @echo ' docker-image-IMAGE: Build image "IMAGE".'
> @echo ' docker-run: For manually running a "TEST" with "IMAGE"'
> @echo
> - @echo 'Available container images:'
> - @echo ' $(DOCKER_IMAGES)'
> + @echo 'Available built container images:'
> + @echo ' $(DOCKER_BUILT_IMAGES)'
> + @echo
> + @echo 'Available (but unbuilt) container images:'
> + @echo ' $(DOCKER_UNBUILT_IMAGES)'
> @echo
> @echo 'Available tests:'
> @echo ' $(DOCKER_TESTS)'
> --
> 2.10.1
>
>
next prev parent reply other threads:[~2016-10-31 2:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 16:33 [Qemu-devel] [PATCH 0/6] Expand the building of qemu-user docker images Alex Bennée
2016-10-28 16:33 ` [Qemu-devel] [PATCH 1/6] tests/docker/Makefile.include: fix diff-index call Alex Bennée
2016-10-31 2:19 ` Fam Zheng
2016-10-31 11:55 ` Alex Bennée
2016-11-01 10:02 ` Alex Bennée
2016-11-01 10:38 ` Fam Zheng
2016-11-01 11:41 ` Alex Bennée
2016-10-28 16:33 ` [Qemu-devel] [PATCH 2/6] tests/docker/test-user: a simple linux-user test Alex Bennée
2016-10-31 2:20 ` Fam Zheng
2016-10-28 16:33 ` [Qemu-devel] [PATCH 3/6] tests/docker: add optional libs to travis.docker Alex Bennée
2016-10-31 2:23 ` Fam Zheng
2016-10-28 16:33 ` [Qemu-devel] [PATCH 4/6] tests/docker/Makefile: Add a rule for Debian user images Alex Bennée
2016-10-28 16:33 ` [Qemu-devel] [PATCH 5/6] tests/docker/docker.py: expand images command Alex Bennée
2016-10-31 2:28 ` Fam Zheng
2016-10-28 16:33 ` [Qemu-devel] [PATCH 6/6] tests/docker/Makefile.include: expand docker help text Alex Bennée
2016-10-31 2:34 ` Fam Zheng [this message]
2016-10-31 2:41 ` [Qemu-devel] [PATCH 0/6] Expand the building of qemu-user docker images Fam Zheng
2016-10-31 11:40 ` Alex Bennée
2016-10-31 13:39 ` 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=20161031023423.GI30303@lemon \
--to=famz@redhat.com \
--cc=alex.bennee@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.