From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Willian Rampazzo" <willianr@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: [PATCH 1/2] tests: Add 'fetch-acceptance' rule
Date: Fri, 24 Jul 2020 09:35:23 +0200 [thread overview]
Message-ID: <20200724073524.26589-2-f4bug@amsat.org> (raw)
In-Reply-To: <20200724073524.26589-1-f4bug@amsat.org>
Add a rule to fetch acceptance test assets.
This is particularly useful in a CI context, when a single job
can fetch and save the cache so other jobs reuse it directly.
It is also useful to measure the time spent downloading the
assets versus the time spent running the tests.
Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
---
tests/Makefile.include | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/tests/Makefile.include b/tests/Makefile.include
index c7e4646ded..238974d8da 100644
--- a/tests/Makefile.include
+++ b/tests/Makefile.include
@@ -944,6 +944,15 @@ get-vm-image-fedora-31-%: check-venv
# download all vm images, according to defined targets
get-vm-images: check-venv $(patsubst %,get-vm-image-fedora-31-%, $(FEDORA_31_DOWNLOAD))
+# fetch acceptance test assets
+fetch-acceptance: check-venv
+ $(call quiet-command, \
+ $(TESTS_VENV_DIR)/bin/python -m avocado \
+ $(if $(V),--show=$(AVOCADO_SHOW)) \
+ assets fetch \
+ $(wildcard tests/acceptance/*.py), \
+ "AVOCADO", "tests/acceptance")
+
check-acceptance: check-venv $(TESTS_RESULTS_DIR) get-vm-images
$(call quiet-command, \
$(TESTS_VENV_DIR)/bin/python -m avocado \
--
2.21.3
next prev parent reply other threads:[~2020-07-24 7:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 7:35 [PATCH 0/2] tests: Add 'fetch-acceptance' rule Philippe Mathieu-Daudé
2020-07-24 7:35 ` Philippe Mathieu-Daudé [this message]
2020-07-24 19:00 ` [PATCH 1/2] " Wainer dos Santos Moschetta
2020-07-24 7:35 ` [PATCH 2/2] tests: Exclude 'boot_linux.py' from fetch-acceptance rule Philippe Mathieu-Daudé
2020-07-24 18:26 ` Wainer dos Santos Moschetta
2020-07-24 18:47 ` Willian Rampazzo
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=20200724073524.26589-2-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=willianr@redhat.com \
/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).