qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: peter.maydell@linaro.org
Cc: "Fam Zheng" <fam@euphon.net>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	qemu-devel@nongnu.org
Subject: [PULL 04/14] travis.yml: Drop the superfluous Python 3.6 build
Date: Fri,  2 Oct 2020 12:36:35 +0100	[thread overview]
Message-ID: <20201002113645.17693-5-alex.bennee@linaro.org> (raw)
In-Reply-To: <20201002113645.17693-1-alex.bennee@linaro.org>

From: Thomas Huth <thuth@redhat.com>

Python 3.6 is already the default Python in the jobs that are based
on Ubuntu Bionic, so it does not make much sense to test this again
separately.

Signed-off-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20200918103430.297167-7-thuth@redhat.com>
Message-Id: <20200925154027.12672-8-alex.bennee@linaro.org>

diff --git a/.travis.yml b/.travis.yml
index 65b825ff64..990dd11e6f 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -262,14 +262,6 @@ jobs:
       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)"
       dist: bionic
-- 
2.20.1



  parent reply	other threads:[~2020-10-02 11:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02 11:36 [PULL 00/14] testing updates (python, plugins) Alex Bennée
2020-10-02 11:36 ` [PULL 01/14] migration: Silence compiler warning in global_state_store_running() Alex Bennée
2020-10-02 11:36 ` [PULL 02/14] travis.yml: Drop the default softmmu builds Alex Bennée
2020-10-02 11:36 ` [PULL 03/14] travis.yml: Update Travis to use Bionic and Focal instead of Xenial Alex Bennée
2020-10-02 11:36 ` Alex Bennée [this message]
2020-10-02 11:36 ` [PULL 05/14] travis.yml: Drop the Python 3.5 build Alex Bennée
2020-10-02 11:36 ` [PULL 06/14] tests/docker: Use Fedora containers for MinGW cross-builds in the gitlab-CI Alex Bennée
2020-10-02 11:36 ` [PULL 07/14] gitlab-ci: Remove the Debian9-based containers and containers-layer3 Alex Bennée
2020-10-02 11:36 ` [PULL 08/14] tests/docker: Update the tricore container to debian 10 Alex Bennée
2020-10-02 11:36 ` [PULL 09/14] shippable.yml: Remove the Debian9-based MinGW cross-compiler tests Alex Bennée
2020-10-02 11:36 ` [PULL 10/14] tests/docker: Remove old Debian 9 containers Alex Bennée
2023-06-23 22:29   ` Philippe Mathieu-Daudé
2023-06-24 14:17     ` Philippe Mathieu-Daudé
2020-10-02 11:36 ` [PULL 11/14] gitlab-ci: Increase the timeout for the cross-compiler builds Alex Bennée
2020-10-02 11:36 ` [PULL 12/14] configure: Bump the minimum required Python version to 3.6 Alex Bennée
2020-10-02 11:36 ` [PULL 13/14] gitlab: move linux-user plugins test across to gitlab Alex Bennée
2020-10-02 11:36 ` [PULL 14/14] gitlab: split deprecated job into build/check stages Alex Bennée
2020-10-02 13:29 ` [PULL 00/14] testing updates (python, plugins) Peter Maydell

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=20201002113645.17693-5-alex.bennee@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=fam@euphon.net \
    --cc=peter.maydell@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).