QEMU-Devel Archive on lore.kernel.org
 help / color / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"John Snow" <jsnow@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
	mdroth@linux.vnet.ibm.com, Eduardo Habkost <ehabkost@redhat.com>,
	Cleber Rosa <cleber@redhat.com>
Subject: [Qemu-devel] Xenial in Travis (was: qapi: Fix code generation with Python 3.5)
Date: Mon, 20 Jan 2020 06:46:00 +0100
Message-ID: <ccbe1f43-f3ba-167e-1f42-bb79ecdcacbb@redhat.com> (raw)
In-Reply-To: <dc9826a5-63a8-9529-838b-aec2fbb66ea6@redhat.com>

On 18/01/2020 09.29, Philippe Mathieu-Daudé wrote:
[...]
> This broke 29 of the 32 Travis jobs we have:
> 
> https://travis-ci.org/qemu/qemu/builds/637999366
> 
> Since we started to use Travis CI, it catched quite some bugs...
> 
> I think it is important to add in the equation we also depend of our CIs.

Thinking about the state of our Travis CI ... The Travis CI jobs that
broke are still running Ubuntu Xenial (v16.04). According to our support
policy, we will stop supporting Xenial two years after v18.04 LTS has
been released, i.e. in April this year. So we have to update our Travis
CI jobs to a newer version with a newer Python very soon anyway - the
question is here only whether we update to v18.04 (with the broken
libssh version that we don't support in QEMU), or rather directly to
v20.04 (which might take a while 'till it shows up as an option in
Travis)...

 Thomas



  reply index

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 20:25 [PATCH] qapi: Fix code generation with Python 3.5 Markus Armbruster
2020-01-16 21:17 ` John Snow
2020-01-17  7:07   ` Markus Armbruster
2020-01-17 19:41     ` John Snow
2020-01-18  6:54       ` Markus Armbruster
2020-02-07 21:54         ` Eduardo Habkost
2020-01-18  8:29       ` Philippe Mathieu-Daudé
2020-01-20  5:46         ` Thomas Huth [this message]
2020-01-17  9:34 ` Thomas Huth
2020-01-17 10:49   ` Markus Armbruster
2020-01-18  8:33     ` Philippe Mathieu-Daudé
2020-01-19 11:23       ` Philippe Mathieu-Daudé
2020-01-20 10:52 ` Alex Bennée
2020-01-20 12:53 ` 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=ccbe1f43-f3ba-167e-1f42-bb79ecdcacbb@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=cleber@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=peter.maydell@linaro.org \
    --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

QEMU-Devel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/qemu-devel/0 qemu-devel/git/0.git
	git clone --mirror https://lore.kernel.org/qemu-devel/1 qemu-devel/git/1.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 qemu-devel qemu-devel/ https://lore.kernel.org/qemu-devel \
		qemu-devel@nongnu.org
	public-inbox-index qemu-devel

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.nongnu.qemu-devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git