From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Fam Zheng" <fam@euphon.net>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH 2/2] travis.yml: Drop the Python 3.5 and 3.6 builds
Date: Sun, 23 Aug 2020 08:54:36 +0200 [thread overview]
Message-ID: <2be38eb3-483a-2539-a1e4-2d4e532328cd@redhat.com> (raw)
In-Reply-To: <20200805184926.15071-1-thuth@redhat.com>
On 05/08/2020 20.49, Thomas Huth wrote:
> Python 3.5 is already the default in Ubuntu Xenial (which we use for
> most jobs on Travis), and Python 3.6 is the default on Ubuntu Bionic
> (which we use for the s390x jobs on Travis for example already), so
> explicitely defining tests for Python 3.5 and 3.6 seems redundant.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> .travis.yml | 17 -----------------
> 1 file changed, 17 deletions(-)
>
> diff --git a/.travis.yml b/.travis.yml
> index 18290bc51d..b4c603f0ec 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -258,23 +258,6 @@ jobs:
> - TEST_CMD=""
>
>
> - # Python builds
> - - name: "GCC Python 3.5 (x86_64-softmmu)"
> - env:
> - - CONFIG="--target-list=x86_64-softmmu"
> - - CACHE_NAME="${TRAVIS_BRANCH}-linux-gcc-default"
> - language: python
> - python: 3.5
> -
> -
> - - name: "GCC Python 3.6 (x86_64-softmmu)"
> - env:
> - - CONFIG="--target-list=x86_64-softmmu"
> - - CACHE_NAME="${TRAVIS_BRANCH}-linux-gcc-default"
> - language: python
> - python: 3.6
> -
> -
> # Using newer GCC with sanitizers
> - name: "GCC9 with sanitizers (softmmu)"
> addons:
>
Ping?
Thomas
next prev parent reply other threads:[~2020-08-23 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 18:49 [PATCH 2/2] travis.yml: Drop the Python 3.5 and 3.6 builds Thomas Huth
2020-08-23 6:54 ` Thomas Huth [this message]
2020-09-05 12:14 ` 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=2be38eb3-483a-2539-a1e4-2d4e532328cd@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=fam@euphon.net \
--cc=philmd@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).