From: Fam Zheng <famz@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: cota@braap.org, berrange@redhat.com, f4bug@amsat.org,
richard.henderson@linaro.org, balrogg@gmail.com,
aurelien@aurel32.net, agraf@suse.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for 3.0 09/10] docker: add test-unit runner
Date: Tue, 10 Jul 2018 15:04:46 +0800 [thread overview]
Message-ID: <20180710070446.GM17581@lemon.usersys.redhat.com> (raw)
In-Reply-To: <20180709152117.21585-10-alex.bennee@linaro.org>
On Mon, 07/09 16:21, Alex Bennée wrote:
> This test doesn't even build QEMU, it just runs all the unit tests.
> Intended to make checking unit tests on all docker images easier.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> tests/docker/test-unit | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
> create mode 100755 tests/docker/test-unit
>
> diff --git a/tests/docker/test-unit b/tests/docker/test-unit
> new file mode 100755
> index 0000000000..be0d90d748
> --- /dev/null
> +++ b/tests/docker/test-unit
> @@ -0,0 +1,19 @@
> +#!/bin/bash
> +#
> +# Build and run the unit tests
> +#
> +# Copyright (c) 2018 Linaro Ltd.
> +#
> +# Authors:
> +# Alex Bennée <alex.bennee@linaro.org>
> +#
> +# This work is licensed under the terms of the GNU GPL, version 2
> +# or (at your option) any later version. See the COPYING file in
> +# the top-level directory.
> +
> +. common.rc
> +
> +cd "$BUILD_DIR"
> +
> +configure_qemu
This reads a bit unusual and counter-intuitive: how could configure_qemu succeed
when the env cannot actually build it? Does configure_qemu fail but the side
effects needed to run build and run unit tests are done anyway? Either way,
please add a comment explaining what is happening here.
Also, should we test the exit code of configure_qemu?
> +check_qemu check-unit
> --
> 2.17.1
>
next prev parent reply other threads:[~2018-07-10 7:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 15:21 [Qemu-devel] [PATCH for 3.0 00/10] various docker fixes Alex Bennée
2018-07-09 15:21 ` [Qemu-devel] [PATCH for 3.0 01/10] tests/.gitignore: don't ignore docker tests Alex Bennée
2018-07-10 6:57 ` Fam Zheng
2018-07-10 7:54 ` Alex Bennée
2018-07-10 8:36 ` Fam Zheng
2018-07-10 20:50 ` Philippe Mathieu-Daudé
2018-07-09 15:21 ` [Qemu-devel] [PATCH for 3.0 02/10] docker: debian-tricore add git tools Alex Bennée
2018-07-10 20:44 ` Philippe Mathieu-Daudé
2018-07-11 0:07 ` Philippe Mathieu-Daudé
2018-07-12 10:44 ` Alex Bennée
2018-07-09 15:21 ` [Qemu-devel] [PATCH for 3.0 03/10] docker: fail more gracefully on docker.py check Alex Bennée
2018-07-10 20:44 ` Philippe Mathieu-Daudé
2018-07-09 15:21 ` [Qemu-devel] [PATCH for 3.0 04/10] docker: split configure_qemu from build_qemu Alex Bennée
2018-07-09 15:21 ` [Qemu-devel] [PATCH for 3.0 05/10] docker: move make check into check_qemu helper Alex Bennée
2018-07-10 6:59 ` Fam Zheng
2018-07-09 15:21 ` [Qemu-devel] [PATCH for 3.0 06/10] docker: gracefully skip check_qemu Alex Bennée
2018-07-09 15:21 ` [Qemu-devel] [PATCH for 3.0 07/10] docker: Makefile.include don't include partial images Alex Bennée
2018-07-09 15:21 ` [Qemu-devel] [PATCH for 3.0 08/10] docker: disable debian-powerpc-user-cross Alex Bennée
2018-07-09 15:21 ` [Qemu-devel] [PATCH for 3.0 09/10] docker: add test-unit runner Alex Bennée
2018-07-10 7:04 ` Fam Zheng [this message]
2018-07-12 10:20 ` Alex Bennée
2018-07-09 15:21 ` [Qemu-devel] [PATCH for 3.0 10/10] docker: add expansion for docker-test-FOO to Makefile.include Alex Bennée
2018-07-10 20:49 ` Philippe Mathieu-Daudé
2018-07-10 21:04 ` Alex Bennée
2018-07-11 1:31 ` Fam Zheng
2018-07-12 8:41 ` Alex Bennée
2018-07-10 7:06 ` [Qemu-devel] [PATCH for 3.0 00/10] various docker fixes Fam Zheng
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=20180710070446.GM17581@lemon.usersys.redhat.com \
--to=famz@redhat.com \
--cc=agraf@suse.de \
--cc=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=balrogg@gmail.com \
--cc=berrange@redhat.com \
--cc=cota@braap.org \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 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).