From: "Alex Bennée" <alex.bennee@linaro.org>
To: peter.maydell@linaro.org
Cc: "Richard Henderson" <richard.henderson@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org
Subject: [PULL 4/7] docs/devel: expand on use of containers to build tests
Date: Wed, 24 Feb 2021 11:49:23 +0000 [thread overview]
Message-ID: <20210224114926.6303-5-alex.bennee@linaro.org> (raw)
In-Reply-To: <20210224114926.6303-1-alex.bennee@linaro.org>
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>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>
Message-Id: <20210222101455.12640-5-alex.bennee@linaro.org>
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
-----------------------
--
2.20.1
next prev parent reply other threads:[~2021-02-24 11:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 11:49 [PULL 0/7] testing updates (build, docs, dumps) Alex Bennée
2021-02-24 11:49 ` [PULL 1/7] meson.build: expose TCG cross compiler information in summary Alex Bennée
2021-02-24 11:49 ` [PULL 2/7] docker: Bump Fedora images to release 33 Alex Bennée
2021-02-24 11:49 ` [PULL 3/7] tests/acceptance: allow a "graceful" failing for virtio-gpu test Alex Bennée
2021-02-24 11:49 ` Alex Bennée [this message]
2021-02-24 11:49 ` [PULL 5/7] docs/devel: update the container based tests Alex Bennée
2021-02-24 11:49 ` [PULL 6/7] docs/devel: add forward reference to check-tcg Alex Bennée
2021-02-24 11:49 ` [PULL 7/7] docs: move CODING_STYLE into the developer documentation Alex Bennée
2021-03-02 15:17 ` [PULL 0/7] testing updates (build, docs, dumps) Peter Maydell
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=20210224114926.6303-5-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 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).