From: David Marchand <david.marchand@redhat.com>
To: Andrzej Ostruszka <amo@semihalf.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] ci: update travis to use bionic
Date: Sun, 19 Jan 2020 18:36:21 +0100 [thread overview]
Message-ID: <CAJFAV8wWOjwv8689kwq7_tTmjr11_zWdPMwTFJNjuUw8pqMzQQ@mail.gmail.com> (raw)
In-Reply-To: <8eff1b76-e0f3-72ce-57b7-3bf23602a3b1@semihalf.com>
On Tue, Dec 17, 2019 at 4:27 PM Andrzej Ostruszka <amo@semihalf.com> wrote:
>
> On 12/17/19 12:42 PM, Kevin Laatz wrote:
> > Currently, the Travis CI is using Ubuntu 16.04 LTS (Xenial) which is
> > becoming increasingly outdated. This patch updates Travis to use Ubuntu
> > 18.04 LTS (Bionic) which will give us the benefit of more up-to-date
> > packages being availble and the newer features that come with them.
>
> Acked-by: Andrzej Ostruszka <amo@semihalf.com>
>
> But I do have a question - should this come together with removal of
> extra sources/packages added just to overcome building problems
> resulting from outdated distro? Or this should be responsibility of
> person that added those (e.g. I've added gcc-7 from
> ubuntu-toolchain/r-test for LTO builds)
We disabled the LTO job in Travis on 11/08:
https://git.dpdk.org/dpdk/commit/?id=20d3f48be1d1
Were you referring to something else?
Thanks.
--
David Marchand
next prev parent reply other threads:[~2020-01-19 17:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 11:42 Kevin Laatz
2019-12-17 14:44 ` Aaron Conole
2019-12-17 15:04 ` Laatz, Kevin
2019-12-17 18:03 ` Aaron Conole
2019-12-19 16:12 ` Laatz, Kevin
2019-12-17 15:26 ` Andrzej Ostruszka
2020-01-19 17:36 ` David Marchand [this message]
2020-01-19 18:20 ` David Marchand
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=CAJFAV8wWOjwv8689kwq7_tTmjr11_zWdPMwTFJNjuUw8pqMzQQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=amo@semihalf.com \
--cc=dev@dpdk.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).