From: Thomas Huth <thuth@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH] travis: remove TCI test
Date: Wed, 23 Sep 2020 18:04:58 +0200 [thread overview]
Message-ID: <9f33653a-30bc-ca38-cec6-c0fbe17cbea0@redhat.com> (raw)
In-Reply-To: <20200923151030.1613449-1-pbonzini@redhat.com>
On 23/09/2020 17.10, Paolo Bonzini wrote:
> The TCI test is already performed on gitlab CI, and it fails because
> Travis tests (generally) disable tools and therefore do not have
> "make check-qtest". Just remove it.
Huh? Where is it failing? It currently seems to work fine:
https://travis-ci.org/github/qemu/qemu/jobs/729440748
Anyway, since we already have similar job in the Gitlab-CI, I think it's
ok to remove it from Travis, so with the commit message tweaked:
Acked-by: Thomas Huth <thuth@redhat.com>
> Cc: Thomas Huth <thuth@redhat.com>
> Cc: Alex Bennée <alex.bennee@linaro.org>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> .travis.yml | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/.travis.yml b/.travis.yml
> index c75221dca3..5811215957 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -239,14 +239,6 @@ jobs:
> - TEST_CMD=""
>
>
> - # Check the TCG interpreter (TCI)
> - - name: "GCC TCI"
> - env:
> - - CONFIG="--enable-debug-tcg --enable-tcg-interpreter --disable-kvm --disable-containers
> - --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
> - name: "GCC trace log,simple,syslog (user)"
> env:
>
next prev parent reply other threads:[~2020-09-23 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 15:10 [PATCH] travis: remove TCI test Paolo Bonzini
2020-09-23 16:04 ` Thomas Huth [this message]
2020-09-23 16:26 ` Paolo Bonzini
2020-09-23 16:31 ` 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=9f33653a-30bc-ca38-cec6-c0fbe17cbea0@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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).