From: Wainer dos Santos Moschetta <wainersm@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>, qemu-devel@nongnu.org
Cc: "Willian Rampazzo" <willianr@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Cleber Rosa" <crosa@redhat.com>
Subject: Re: [PATCH 1/2] tests: Add 'fetch-acceptance' rule
Date: Fri, 24 Jul 2020 16:00:32 -0300 [thread overview]
Message-ID: <cf93f6be-c25b-7ba3-96ee-0ab8f6b4b9e7@redhat.com> (raw)
In-Reply-To: <20200724073524.26589-2-f4bug@amsat.org>
Hello,
On 7/24/20 4:35 AM, Philippe Mathieu-Daudé wrote:
> 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
This new target misses an entry on check-help.
> + $(call quiet-command, \
> + $(TESTS_VENV_DIR)/bin/python -m avocado \
> + $(if $(V),--show=$(AVOCADO_SHOW)) \
> + assets fetch \
Perhaps pass '--ignore-errors' so that intermittent network failurse
won't disturb the execution (the test will have a second chance to
download the asset later when it executes).
> + $(wildcard tests/acceptance/*.py), \
> + "AVOCADO", "tests/acceptance")
nit: print "Downloading acceptance tests assets" (similar to
get-vm-image-fedora-32-% target).
Talking about get-vm-images...that target is pre-req of
check-acceptance, which makes me think that fetch-acceptance should be
either (for the sake of consistency.) The downside is that - as a
developer running it on my machine - `avocado assets fetch` will attempt
to download artifacts even for those tests which I'm not going to run
anyway. Any opinion?
Regards,
Wainer
> +
> check-acceptance: check-venv $(TESTS_RESULTS_DIR) get-vm-images
> $(call quiet-command, \
> $(TESTS_VENV_DIR)/bin/python -m avocado \
next prev parent reply other threads:[~2020-07-24 19:02 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 ` [PATCH 1/2] " Philippe Mathieu-Daudé
2020-07-24 19:00 ` Wainer dos Santos Moschetta [this message]
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=cf93f6be-c25b-7ba3-96ee-0ab8f6b4b9e7@redhat.com \
--to=wainersm@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).