qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>, "Cleber Rosa" <crosa@redhat.com>
Subject: [Qemu-devel] [PULL 5/9] Travis CI: make specified Python versions usable on jobs
Date: Thu, 17 Jan 2019 18:17:39 -0200	[thread overview]
Message-ID: <20190117201743.20470-6-ehabkost@redhat.com> (raw)
In-Reply-To: <20190117201743.20470-1-ehabkost@redhat.com>

From: Cleber Rosa <crosa@redhat.com>

For the two Python jobs, which seem to have the goal of making sure
QEMU builds successfully on the 3.0-3.6 spectrum of Python 3 versions,
the specified version is only applicable if a Python virtual
environment is used.  To do that, it's necessary to define the
(primary?) language of the job to be Python.

Also, Travis doesn't have a 3.0 Python installation available for the
chosen distro, 3.4 being the lower version available.

Reference: https://docs.travis-ci.com/user/languages/python/#specifying-python-versions
Signed-off-by: Cleber Rosa <crosa@redhat.com>
Message-Id: <20181109150710.31085-4-crosa@redhat.com>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
[ehabkost: Now 3.4 is the lowest Python version available]
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>

fixup! Travis CI: make specified Python versions usable on jobs

Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
---
 .travis.yml | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/.travis.yml b/.travis.yml
index 93fd0164a0..87d9fa971c 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -175,12 +175,14 @@ matrix:
     # Python builds
     - env:
         - CONFIG="--target-list=x86_64-softmmu"
+      language: python
       python:
-        - "3.0"
+        - "3.4"
 
 
     - env:
         - CONFIG="--target-list=x86_64-softmmu"
+      language: python
       python:
         - "3.6"
 
-- 
2.18.0.rc1.1.g3f1ff2140

  parent reply	other threads:[~2019-01-17 20:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17 20:17 [Qemu-devel] [PULL 0/9] Python queue, 2019-01-17 Eduardo Habkost
2019-01-17 20:17 ` [Qemu-devel] [PULL 1/9] scripts/device-crash-test: Remove known crashes Eduardo Habkost
2019-01-17 20:17 ` [Qemu-devel] [PULL 2/9] scripts: Remove unused python imports Eduardo Habkost
2019-01-17 20:17 ` [Qemu-devel] [PULL 3/9] configure: keep track of Python version Eduardo Habkost
2019-01-17 20:17 ` [Qemu-devel] [PULL 4/9] check-venv: use recorded " Eduardo Habkost
2019-01-17 20:17 ` Eduardo Habkost [this message]
2019-01-17 20:17 ` [Qemu-devel] [PULL 6/9] check-help: visual and content improvements Eduardo Habkost
2019-01-17 20:17 ` [Qemu-devel] [PULL 7/9] Acceptance tests: add Linux initrd checking test Eduardo Habkost
2019-01-17 20:17 ` [Qemu-devel] [PULL 8/9] qemu.py: Fix error message when qemu dies from signal Eduardo Habkost
2019-01-17 20:17 ` [Qemu-devel] [PULL 9/9] scripts/replay-dump.py: fix utf-8 mangling Eduardo Habkost
2019-01-18 16:55 ` [Qemu-devel] [PULL 0/9] Python queue, 2019-01-17 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=20190117201743.20470-6-ehabkost@redhat.com \
    --to=ehabkost@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=crosa@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).