From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, thuth@redhat.com,
"Alex Bennée" <alex.bennee@linaro.org>,
"Fam Zheng" <famz@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
programmingkidx@gmail.com, crosa@redhat.com, pbonzini@redhat.com,
rth@twiddle.net
Subject: [Qemu-devel] [PATCH RFC 0/7] Proof of concept to power up "make test" with docker
Date: Fri, 8 Sep 2017 17:16:53 +0800 [thread overview]
Message-ID: <20170908091700.14867-1-famz@redhat.com> (raw)
Recently it was brought up that "make test" is in an orphaned state, and making
it work would be a good thing because it has valuable test coverage for tcg:
https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg04978.html
This RFC is an attempt to use docker to cross build the test binaries that will
be run by qemu-user and meanwhile rename it from "make test" to "make
check-tcg" to align with the naming convention of other test targets we have.
As the initial version only i386 is converted, not because it's easy, but
because it is a test set that covers the most types of rules we will need
(cross-build, run and compare result).
After these patches, "make check-tcg" will do the i386 tests with the new
rules first (which fails but that's out of the scope of this series), then
continue to do the old "make -C tests/tcg test" command. Once all tests are
moved into the new Makefile.include file, the old Makefile can be dropped.
Fam Zheng (7):
Makefile: Rename TARGET_DIRS to TARGET_LIST
docker: Add "cc" subcommand
docker: Add fedora-i386-cross image
tests: Build fix for hello-i386
tests: Build fix for linux-test
buildsys: Add "check-tcg" target
tests: Move i386 tcg tests to check-tcg
Makefile | 21 ++++---
configure | 2 +-
scripts/create_config | 2 +-
tests/Makefile.include | 3 +-
tests/docker/docker.py | 23 +++++++
tests/docker/dockerfiles/fedora-i386-cross.docker | 13 ++++
tests/tcg/Makefile | 60 ------------------
tests/tcg/Makefile.include | 75 +++++++++++++++++++++++
tests/tcg/hello-i386.c | 1 +
tests/tcg/linux-test.c | 67 +++++++-------------
10 files changed, 149 insertions(+), 118 deletions(-)
create mode 100644 tests/docker/dockerfiles/fedora-i386-cross.docker
create mode 100644 tests/tcg/Makefile.include
--
2.13.5
next reply other threads:[~2017-09-08 9:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 9:16 Fam Zheng [this message]
2017-09-08 9:16 ` [Qemu-devel] [PATCH RFC 1/7] Makefile: Rename TARGET_DIRS to TARGET_LIST Fam Zheng
2017-09-08 9:16 ` [Qemu-devel] [PATCH RFC 2/7] docker: Add "cc" subcommand Fam Zheng
2017-09-08 9:16 ` [Qemu-devel] [PATCH RFC 3/7] docker: Add fedora-i386-cross image Fam Zheng
2017-09-08 9:16 ` [Qemu-devel] [PATCH RFC 4/7] tests: Build fix for hello-i386 Fam Zheng
2017-09-08 9:16 ` [Qemu-devel] [PATCH RFC 5/7] tests: Build fix for linux-test Fam Zheng
2017-09-08 9:16 ` [Qemu-devel] [PATCH RFC 6/7] buildsys: Add "check-tcg" target Fam Zheng
2017-09-08 9:17 ` [Qemu-devel] [PATCH RFC 7/7] tests: Move i386 tcg tests to check-tcg Fam Zheng
2017-09-08 9:26 ` [Qemu-devel] [PATCH RFC 0/7] Proof of concept to power up "make test" with docker no-reply
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=20170908091700.14867-1-famz@redhat.com \
--to=famz@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--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).