From: "Alex Bennée" <alex.bennee@linaro.org>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: pierrick.bouvier@oss.qualcomm.com, qemu-devel@nongnu.org
Subject: Re: [PATCH] tests/docker: fix ccache directory variable expansion
Date: Wed, 16 Sep 2026 17:53:22 +0100 [thread overview]
Message-ID: <87pkyd87el.fsf@draig.linaro.org> (raw)
In-Reply-To: <20260915072403.347639-1-anders.roxell@linaro.org> (Anders Roxell's message of "Tue, 15 Sep 2026 09:24:03 +0200")
Anders Roxell <anders.roxell@linaro.org> writes:
> DOCKER_QEMU_CCACHE_DIR is missing $() around DOCKER_QEMU_CACHE_DIR, so
> $HOME/.cache/qemu is never created. podman then fails to mount it:
>
> Error: statfs /home/user/.cache/qemu: no such file or directory
>
> It only works if the directory already exists. Add the missing $().
>
> Fixes: 8a1975e4d44b ("tests/docker: expose $HOME/.cache/qemu as docker volume")
> Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
> ---
> tests/docker/Makefile.include | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/docker/Makefile.include b/tests/docker/Makefile.include
> index 0adddb6a5c62..e506add8aa8b 100644
> --- a/tests/docker/Makefile.include
> +++ b/tests/docker/Makefile.include
> @@ -199,7 +199,7 @@ docker-help: docker
> # Where QEMU caches build artefacts
> DOCKER_QEMU_CACHE_DIR := $$HOME/.cache/qemu
> # Use a global constant ccache directory to speed up repetitive builds
> -DOCKER_QEMU_CCACHE_DIR := DOCKER_QEMU_CACHE_DIR/docker-ccache
> +DOCKER_QEMU_CCACHE_DIR := $(DOCKER_QEMU_CACHE_DIR)/docker-ccache
>
> # This rule if for directly running against an arbitrary docker target.
> # It is called by the expanded docker targets (e.g. make
Queued to testing/next, thanks.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
prev parent reply other threads:[~2026-09-16 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 7:24 [PATCH] tests/docker: fix ccache directory variable expansion Anders Roxell
2026-09-16 16:53 ` Alex Bennée [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=87pkyd87el.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=anders.roxell@linaro.org \
--cc=pierrick.bouvier@oss.qualcomm.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 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.