From: "Laatz, Kevin" <kevin.laatz@intel.com>
To: Aaron Conole <aconole@redhat.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ci: update travis to use bionic
Date: Tue, 17 Dec 2019 15:04:19 +0000 [thread overview]
Message-ID: <a69805f9-4ac2-4ff4-6c49-1429034d1c99@intel.com> (raw)
In-Reply-To: <f7tfthjovup.fsf@dhcp-25.97.bos.redhat.com>
On 17/12/2019 14:44, Aaron Conole wrote:
> Kevin Laatz <kevin.laatz@intel.com> writes:
>
>> 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.
>>
>> Signed-off-by: Kevin Laatz <kevin.laatz@intel.com>
>> ---
>> .travis.yml | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/.travis.yml b/.travis.yml
>> index 8f90d06f2..6e0626353 100644
>> --- a/.travis.yml
>> +++ b/.travis.yml
>> @@ -4,7 +4,7 @@ compiler:
>> - gcc
>> - clang
>>
>> -dist: xenial
>> +dist: bionic
> This LGTM.
>
>> os:
>> - linux
>> @@ -21,7 +21,7 @@ aarch64_packages: &aarch64_packages
>>
>> extra_packages: &extra_packages
>> - *required_packages
>> - - [libbsd-dev, libpcap-dev, libcrypto++-dev, libjansson4]
>> + - [libbsd-dev, libpcap-dev, libcrypto++-dev, libjansson4, abigail-tools]
> Will adding the abigail-tools automatically invoke the ABI checks?
> Otherwise, maybe it's best to save this for a future commit.
>
> I'll look for the robot build when it comes by. Thanks!
Yes, the meson option that will be introduced with the "Add ABI
compatibility checks to the meson build" [1] patch set will be set to
"auto" meaning the checks will run if abidiff is found.
[1] http://patches.dpdk.org/project/dpdk/list/?series=7830
>
>> build_32b_packages: &build_32b_packages
>> - *required_packages
next prev parent reply other threads:[~2019-12-17 15:04 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 [this message]
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
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=a69805f9-4ac2-4ff4-6c49-1429034d1c99@intel.com \
--to=kevin.laatz@intel.com \
--cc=aconole@redhat.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).