From: "Alex Bennée" <alex.bennee@linaro.org>
To: famz@redhat.com
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Subject: [Qemu-devel] [PATCH v3 5/5] tests/docker/Makefile.include: remove verification targets
Date: Tue, 11 Oct 2016 17:16:25 +0100 [thread overview]
Message-ID: <20161011161625.9070-6-alex.bennee@linaro.org> (raw)
In-Reply-To: <20161011161625.9070-1-alex.bennee@linaro.org>
As it turns out there are a bunch of verification targets we don't hit
because of other matching patterns in rules.mk. Drop the verification
steps all together.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
---
v3
- new for v3, could be squashed with previous commit
---
tests/docker/Makefile.include | 34 +++-------------------------------
1 file changed, 3 insertions(+), 31 deletions(-)
diff --git a/tests/docker/Makefile.include b/tests/docker/Makefile.include
index ba7c984..925f711 100644
--- a/tests/docker/Makefile.include
+++ b/tests/docker/Makefile.include
@@ -134,40 +134,12 @@ docker-run: docker-qemu-src
/var/tmp/qemu/run \
$(TEST), " RUN $(TEST) in ${IMAGE}")
+# Run targets:
#
-# Verification targets
-#
-# These targets help verify the test (CMD) and docker tag (IMAGE) are
-# part of the built in set of tests and images. You can still call the
-# docker-run target directly for testsing against arbitary images.
-#
-
-docker-verify-image-%: IMAGE = $(shell echo '$@' | sed -e 's/docker-verify-image-\([^@]*\)@\(.*\)/\2/')
-docker-verify-image-%:
- @if test -z "$(IMAGE)"; \
- then echo "Invalid image"; exit 1; \
- fi
- $(if $(filter $(IMAGE), $(DOCKER_IMAGES)), , \
- echo "$(IMAGE) is not a known image"; exit 1) \
-
-docker-verify-test-%: CMD = $(shell echo '$@' | sed -e 's/docker-verify-test-\([^@]*\)@\(.*\)/\1/')
-docker-verify-test-%:
- @if test -z "$(CMD)"; \
- then echo "Invalid test"; exit 1; \
- fi
- $(if $(filter $(CMD), $(DOCKER_TESTS)), , \
- echo "$(CMD) is not a known test"; exit 1)
-
-# Run targets
-#
-# This will take a target such as docker-test-foo@bar and verify that:
-# - the test test-foo is a known test
-# - the image bar is a known image
-#
-# It will then call the docker-run
+# Of the form docker-TEST-FOO@IMAGE-BAR which will then be expanded into a call to "make docker-run"
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-verify-image-% docker-verify-test-%
+docker-run-%:
@make docker-run TEST=$(CMD) IMAGE=qemu:$(IMAGE)
docker-clean:
--
2.9.3
next prev parent reply other threads:[~2016-10-11 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 16:16 [Qemu-devel] [PATCH v3 0/5] generic docker run patches Alex Bennée
2016-10-11 16:16 ` [Qemu-devel] [PATCH v3 1/5] tests/docker: add travis dockerfile Alex Bennée
2016-10-11 16:16 ` [Qemu-devel] [PATCH v3 2/5] tests/docker: test-build script Alex Bennée
2016-10-11 16:16 ` [Qemu-devel] [PATCH v3 3/5] tests/docker: make test-mingw honour TARGET_LIST Alex Bennée
2016-10-11 16:16 ` [Qemu-devel] [PATCH v3 4/5] tests/docker/Makefile.include: add a generic docker-run target Alex Bennée
2016-10-11 16:16 ` Alex Bennée [this message]
2016-10-12 1:10 ` [Qemu-devel] [PATCH v3 0/5] generic docker run patches 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=20161011161625.9070-6-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=famz@redhat.com \
--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).