From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v2 3/4] tests/docker: allow display of docker output
Date: Fri, 10 Jul 2026 12:36:52 +0100 [thread overview]
Message-ID: <87qzlbqdnv.fsf@draig.linaro.org> (raw)
In-Reply-To: <20260210163556.713841-4-berrange@redhat.com> ("Daniel P. Berrangé"'s message of "Tue, 10 Feb 2026 16:35:55 +0000")
Daniel P. Berrangé <berrange@redhat.com> writes:
> The --quiet command is used with docker unless V=1 is passed to make,
> and as a result stdout from docker is never visible by default, making
> it hard to diagnose failures building / running containers.
>
> Meanwhile passing V=1 is undesirable as that makes the entire build
> system verbose.
>
> Introduce a $(DOCKER_V) make variable which is initialized from $(V)
>
> It is thus possible to display docker output without also enabling
> make verbose output.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2026-07-10 11:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 16:35 [PATCH v2 0/4] tests/docker: improve detection of docker/podman Daniel P. Berrangé
2026-02-10 16:35 ` [PATCH v2 1/4] tests/docker: improve handling of docker probes Daniel P. Berrangé
2026-02-10 16:35 ` [PATCH v2 2/4] tests/docker: add support for podman remote access Daniel P. Berrangé
2026-03-02 7:51 ` Thomas Huth
2026-07-09 14:48 ` Pierrick Bouvier
2026-07-09 15:40 ` Daniel P. Berrangé
2026-07-09 15:55 ` Pierrick Bouvier
2026-07-09 16:01 ` Daniel P. Berrangé
2026-07-09 16:04 ` Pierrick Bouvier
2026-07-09 16:15 ` Daniel P. Berrangé
2026-07-09 16:13 ` Daniel P. Berrangé
2026-07-09 16:24 ` Pierrick Bouvier
2026-07-10 8:06 ` Daniel P. Berrangé
2026-07-10 11:47 ` Alex Bennée
2026-07-10 11:52 ` Daniel P. Berrangé
2026-07-10 18:20 ` Pierrick Bouvier
2026-07-13 8:32 ` Daniel P. Berrangé
2026-07-13 16:01 ` Pierrick Bouvier
2026-02-10 16:35 ` [PATCH v2 3/4] tests/docker: allow display of docker output Daniel P. Berrangé
2026-03-02 8:07 ` Thomas Huth
2026-07-10 11:36 ` Alex Bennée [this message]
2026-02-10 16:35 ` [PATCH v2 4/4] gitlab: ensure docker output is always displayed in CI Daniel P. Berrangé
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=87qzlbqdnv.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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 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.