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>
Cc: qemu-trivial@nongnu.org,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH] travis.yml: Run tcg tests with tci
Date: Thu, 28 Nov 2019 09:13:05 +0100	[thread overview]
Message-ID: <02c92ddf-e65a-2d2d-40fa-027aa4e4c558@redhat.com> (raw)
In-Reply-To: <87zhghf9lg.fsf@linaro.org>

On 27/11/2019 19.38, Alex Bennée wrote:
> 
> Thomas Huth <thuth@redhat.com> writes:
> 
>> So far we only have compile coverage for tci. But since commit
>> 2f160e0f9797c7522bfd0d09218d0c9340a5137c ("tci: Add implementation
>> for INDEX_op_ld16u_i64") has been included, we can also run the
>> x86 TCG tests with tci, so let's enable them in Travis now.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>>   .travis.yml | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/.travis.yml b/.travis.yml
>> index c09b6a0014..b0b634d484 100644
>> --- a/.travis.yml
>> +++ b/.travis.yml
>> @@ -218,7 +218,7 @@ matrix:
>>       # We manually include builds which we disable "make check" for
> 
> this comment is out of date now (or rather has been for a while)
> 
>>       - env:
>>           - CONFIG="--enable-debug --enable-tcg-interpreter"
> 
> Perhaps as linux-user doesn't add much to testing the TCG we could limit
> by MAIN_SOFTMMU_TARGETS here?

Limiting is a good idea, but I think we should use the architectures 
that are supported by tests/boot-serial-test.c instead.

>> -        - TEST_CMD=""
>> +        - TEST_CMD="make run-tcg-tests-x86_64-softmmu V=1"
> 
> How about "make check-qtest check-tcg"
> > Which will exercise the moderate boot code tests of various
> architectures as well as x86_64 (if we include the --disable-docker
> configure stanza)

I tried "check-tcg" before switching to "run-tcg-tests-x86_64-softmmu", 
but "check-tcg" then resulted in a docker error:

  https://travis-ci.com/huth/qemu/jobs/260949876#L11974

... so looks like we indeed have to use --disable-docker in that case.

I'll have a try and send a v2 if that works out fine.

  Thomas



  parent reply	other threads:[~2019-11-28  8:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27 15:48 [PATCH] travis.yml: Run tcg tests with tci Thomas Huth
2019-11-27 18:08 ` Philippe Mathieu-Daudé
2019-11-27 18:38 ` Alex Bennée
2019-11-27 21:19   ` Philippe Mathieu-Daudé
2019-11-28  8:13   ` Thomas Huth [this message]
2019-11-28 10:16     ` Alex Bennée
2019-11-28 13:33       ` Thomas Huth

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=02c92ddf-e65a-2d2d-40fa-027aa4e4c558@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.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).