qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: fam@euphon.net, berrange@redhat.com, f4bug@amsat.org,
	stefanha@redhat.com, crosa@redhat.com, pbonzini@redhat.com,
	aurelien@aurel32.net
Subject: Re: [PATCH v2 4/6] docs/devel: expand on use of containers to build tests
Date: Mon, 22 Feb 2021 12:39:35 +0100	[thread overview]
Message-ID: <af0dbc9f-890e-36b8-0fcb-e25a6234ffec@redhat.com> (raw)
In-Reply-To: <20210222101455.12640-5-alex.bennee@linaro.org>

On 22/02/2021 11.14, Alex Bennée wrote:
> Expand on the usage of containers for building tests and why we have
> some that are not used to build QEMU itself.
> 
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Cc: Thomas Huth <thuth@redhat.com>
> ---
>   docs/devel/testing.rst | 21 ++++++++++++++-------
>   1 file changed, 14 insertions(+), 7 deletions(-)
> 
> diff --git a/docs/devel/testing.rst b/docs/devel/testing.rst
> index 00ce16de48..488d4e3537 100644
> --- a/docs/devel/testing.rst
> +++ b/docs/devel/testing.rst
> @@ -272,10 +272,10 @@ Note that the following group names have a special meaning:
>   
>   - disabled: Tests in this group are disabled and ignored by check.
>   
> -.. _docker-ref:
> +.. _container-ref:
>   
> -Docker based tests
> -==================
> +Container based tests
> +=====================
>   
>   Introduction
>   ------------
> @@ -1001,10 +1001,17 @@ for the architecture in question, for example::
>   There is also a ``--cross-cc-flags-ARCH`` flag in case additional
>   compiler flags are needed to build for a given target.
>   
> -If you have the ability to run containers as the user you can also
> -take advantage of the build systems "Docker" support. It will then use
> -containers to build any test case for an enabled guest where there is
> -no system compiler available. See :ref:`docker-ref` for details.
> +If you have the ability to run containers as the user the build system
> +will automatically use them where no system compiler is available. For
> +architectures where we also support building QEMU we will generally
> +use the same container to build tests. However there are a number of
> +additional containers defined that have a minimal cross-build
> +environment that is only suitable for building test cases. Sometimes
> +we may use a bleeding edge distribution for compiler features needed
> +for test cases that aren't yet in the LTS distros we support for QEMU
> +itself.
> +
> +See :ref:`container-ref` for more details.
>   
>   Running subset of tests
>   -----------------------
> 

Reviewed-by: Thomas Huth <thuth@redhat.com>



  reply	other threads:[~2021-02-22 11:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 10:14 [PATCH v2 0/6] testing/next (meson check-tcg, fedora bump, docs) Alex Bennée
2021-02-22 10:14 ` [PATCH v2 1/6] meson.build: expose TCG cross compiler information in summary Alex Bennée
2021-02-22 10:14 ` [PATCH v2 2/6] docker: Bump Fedora images to release 33 Alex Bennée
2021-02-22 10:14 ` [PATCH v2 3/6] tests/acceptance: allow a "graceful" failing for virtio-gpu test Alex Bennée
2021-02-22 15:44   ` Probing Meson for build configurations (was: [PATCH v2 3/6] tests/acceptance: allow a "graceful" failing for virtio-gpu test) Wainer dos Santos Moschetta
2021-02-22 16:05     ` Daniel P. Berrangé
2021-02-22 10:14 ` [PATCH v2 4/6] docs/devel: expand on use of containers to build tests Alex Bennée
2021-02-22 11:39   ` Thomas Huth [this message]
2021-02-22 10:14 ` [PATCH v2 5/6] docs/devel: update the container based tests Alex Bennée
2021-02-22 11:46   ` Thomas Huth
2021-02-22 12:14     ` Alex Bennée
2021-02-22 12:15       ` Thomas Huth
2021-02-22 10:14 ` [PATCH v2 6/6] docs/devel: add forward reference to check-tcg Alex Bennée
2021-02-22 11:36   ` Philippe Mathieu-Daudé
2021-02-22 12:16   ` Thomas Huth
2021-02-24  3:33 ` [PATCH v2 0/6] testing/next (meson check-tcg, fedora bump, docs) Richard Henderson

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=af0dbc9f-890e-36b8-0fcb-e25a6234ffec@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=aurelien@aurel32.net \
    --cc=berrange@redhat.com \
    --cc=crosa@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=fam@euphon.net \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).