From: Stefan Weil <sw@weilnetz.de>
To: "Thomas Huth" <thuth@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v2 2/2] travis.yml: Run tcg tests with tci
Date: Thu, 28 Nov 2019 22:06:01 +0100 [thread overview]
Message-ID: <672f7c1a-71d6-5dfa-101a-ed3070be0b05@weilnetz.de> (raw)
In-Reply-To: <20191128153525.2646-3-thuth@redhat.com>
Am 28.11.19 um 16:35 schrieb Thomas Huth:
> So far we only have compile coverage for tci. But since commit
> 2f160e0f9797c7522bfd0d09218d0c9340a5137c ("tci: Add implementation
> for INDEX_op_ld16u_i64") has been included now, we can also run the
> "tcg" and "qtest" tests with tci, so let's enable them in Travis now.
> Since we don't gain much additional test coverage by compiling all
> targets, and TCI is broken e.g. with the Sparc targets, we also limit
As far as I know it is broken with Sparc hosts (not Sparc targets).
I tested without limiting the target list on an x86_64 host, and the
tests passed.
> the target list to a reasonable subset now (which should still get
> us test coverage by tests/boot-serial-test for example).
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> .travis.yml | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/.travis.yml b/.travis.yml
> index c09b6a0014..de7559e777 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -215,10 +215,11 @@ matrix:
> - TEST_CMD=""
>
>
> - # We manually include builds which we disable "make check" for
> + # Check the TCG interpreter (TCI)
> - env:
> - - CONFIG="--enable-debug --enable-tcg-interpreter"
> - - TEST_CMD=""
> + - CONFIG="--enable-debug --enable-tcg-interpreter --disable-containers
You could also --disable-kvm. It should not be needed, and disabling it
might need less build resources.
> + --target-list=alpha-softmmu,arm-softmmu,hppa-softmmu,m68k-softmmu,microblaze-softmmu,moxie-softmmu,ppc-softmmu,s390x-softmmu,x86_64-softmmu"
> + - TEST_CMD="make check-qtest check-tcg V=1"
>
>
> # We don't need to exercise every backend with every front-end
Thank you for adding these tests.
Tested-by: Stefan Weil <sw@weilnetz.de>
next prev parent reply other threads:[~2019-11-28 21:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 15:35 [PATCH v2 0/2] Run tcg tests with tci on Travis Thomas Huth
2019-11-28 15:35 ` [PATCH v2 1/2] configure: allow disable of cross compilation containers Thomas Huth
2019-11-28 20:38 ` Stefan Weil
2019-11-28 15:35 ` [PATCH v2 2/2] travis.yml: Run tcg tests with tci Thomas Huth
2019-11-28 21:06 ` Stefan Weil [this message]
2019-11-28 21:33 ` Stefan Weil
2019-12-03 13:20 ` Thomas Huth
2019-11-29 8:09 ` Thomas Huth
2019-12-03 10:19 ` Alex Bennée
2019-12-04 8:31 ` [PATCH v3] " Thomas Huth
2019-12-04 13:39 ` Richard Henderson
2019-12-04 13:54 ` Alex Bennée
2019-12-04 13:48 ` Alex Bennée
2019-12-04 13:51 ` Thomas Huth
2019-12-04 14:15 ` Alex Bennée
2019-11-28 20:06 ` [PATCH v2 0/2] Run tcg tests with tci on Travis Philippe Mathieu-Daudé
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=672f7c1a-71d6-5dfa-101a-ed3070be0b05@weilnetz.de \
--to=sw@weilnetz.de \
--cc=alex.bennee@linaro.org \
--cc=philmd@redhat.com \
--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 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).