From: Thomas Huth <thuth@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Yoshinori Sato" <ysato@users.sourceforge.jp>,
qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Pavel Dovgalyuk" <pavel.dovgaluk@ispras.ru>,
"Cleber Rosa" <crosa@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v2 4/4] gitlab-ci: Fix Avocado cache usage
Date: Tue, 4 Aug 2020 18:32:52 +0200 [thread overview]
Message-ID: <48e7ef9e-12b9-a970-9fb7-70f87b126fd6@redhat.com> (raw)
In-Reply-To: <877dueml9w.fsf@linaro.org>
On 04/08/2020 18.24, Alex Bennée wrote:
>
> Thomas Huth <thuth@redhat.com> writes:
>
>> In commit 6957fd98dc ("gitlab: add avocado asset caching") we
>> tried to save the Avocado cache (as in commit c1073e44b4 with
>> Travis-CI) however it doesn't work as expected. For some reason
>> Avocado uses /root/avocado_cache/ which we can not select later.
>>
>> Manually generate a Avocado config to force the use of the
>> current job's directory.
>>
>> This patch is based on an earlier version from Philippe Mathieu-Daudé.
>
> Maybe add a Based-on: <msgid>?
Isn't that tag rather used for expressing dependencies between patch
series? See
https://wiki.qemu.org/Contribute/SubmitAPatch#Base_patches_against_current_git_master
?
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> .gitlab-ci.yml | 25 +++++++++++++++++++------
>> 1 file changed, 19 insertions(+), 6 deletions(-)
>>
>> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
>> index e96bcd50f8..9820066379 100644
>> --- a/.gitlab-ci.yml
>> +++ b/.gitlab-ci.yml
>> @@ -47,11 +47,24 @@ include:
>> - find . -type f -exec touch {} +
>> - make $MAKE_CHECK_ARGS
>>
>> -.post_acceptance_template: &post_acceptance
>> +.acceptance_template: &acceptance_definition
>> + cache:
>> + key: "${CI_JOB_NAME}-cache"
>> + paths:
>> + - ${CI_PROJECT_DIR}/avocado-cache
>> + policy: pull-push
>> + before_script:
>> + - mkdir -p ~/.config/avocado
>> + - echo "[datadir.paths]" > ~/.config/avocado/avocado.conf
>> + - echo "cache_dirs = ['${CI_PROJECT_DIR}/avocado-cache']"
>> + >> ~/.config/avocado/avocado.conf
>
> I was hoping there was a neater way to do this with the multiline
> commands but whatever:
I'm still fighting YAML syntax when it comes to such cases ... so I'm
open to suggestions!
> Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
Thanks a lot!
Thomas
prev parent reply other threads:[~2020-08-04 16:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 14:13 [PATCH v2 0/4] Test more in less time in the Gitlab-CI Thomas Huth
2020-07-30 14:13 ` [PATCH v2 1/4] tests/docker: Add python3-venv and netcat to the debian-amd64 container Thomas Huth
2020-08-04 16:07 ` Alex Bennée
2020-07-30 14:13 ` [PATCH v2 2/4] tests/acceptance: Disable the rx sash and arm cubieboard replay test on Gitlab Thomas Huth
2020-08-04 16:09 ` Alex Bennée
2020-07-30 14:13 ` [PATCH v2 3/4] gitlab-ci.yml: Add build-system-debian and build-system-centos jobs Thomas Huth
2020-08-04 16:15 ` Alex Bennée
2020-07-30 14:13 ` [PATCH v2 4/4] gitlab-ci: Fix Avocado cache usage Thomas Huth
2020-08-04 16:24 ` Alex Bennée
2020-08-04 16:32 ` Thomas Huth [this message]
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=48e7ef9e-12b9-a970-9fb7-70f87b126fd6@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=pavel.dovgaluk@ispras.ru \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@redhat.com \
--cc=ysato@users.sourceforge.jp \
/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).