From: David Marchand <david.marchand@redhat.com>
To: thomas@monjalon.net, aconole@redhat.com
Cc: dev@dpdk.org, Michael Santana <maicolgabriel@hotmail.com>
Subject: [dpdk-dev] [PATCH 2/4] ci: fix Travis config warnings
Date: Wed, 19 Feb 2020 20:41:29 +0100 [thread overview]
Message-ID: <20200219194131.29417-3-david.marchand@redhat.com> (raw)
In-Reply-To: <20200219194131.29417-1-david.marchand@redhat.com>
Reading https://config.travis-ci.com/ and using
https://config.travis-ci.com/explore to check changes, we can cleanup
some warnings reported by the config validation options in Travis.
Signed-off-by: David Marchand <david.marchand@redhat.com>
---
.travis.yml | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/.travis.yml b/.travis.yml
index 671447ee8..7c1b2ff1b 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -19,22 +19,22 @@ addons:
packages: &required_packages
- [libnuma-dev, python3-setuptools, python3-wheel, python3-pip, ninja-build]
-aarch64_packages: &aarch64_packages
+_aarch64_packages: &aarch64_packages
- *required_packages
- [gcc-aarch64-linux-gnu, libc6-dev-arm64-cross, pkg-config-aarch64-linux-gnu]
-extra_packages: &extra_packages
+_extra_packages: &extra_packages
- *required_packages
- [libbsd-dev, libpcap-dev, libibverbs-dev, libcrypto++-dev, libfdt-dev, libjansson4]
-libabigail_build_packages: &libabigail_build_packages
+_libabigail_build_packages: &libabigail_build_packages
- [autoconf, automake, libtool, pkg-config, libxml2-dev, libdw-dev]
-build_32b_packages: &build_32b_packages
+_build_32b_packages: &build_32b_packages
- *required_packages
- [gcc-multilib]
-doc_packages: &doc_packages
+_doc_packages: &doc_packages
- [doxygen, graphviz, python3-sphinx]
before_install: ./.ci/${TRAVIS_OS_NAME}-setup.sh
@@ -44,7 +44,7 @@ env:
- DEF_LIB="shared"
- DEF_LIB="shared" RUN_TESTS=1
-matrix:
+jobs:
include:
- env: DEF_LIB="static" BUILD_32BIT=1
compiler: gcc
--
2.23.0
next prev parent reply other threads:[~2020-02-19 19:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 19:41 [dpdk-dev] [PATCH 0/4] Reorganise Travis jobs David Marchand
2020-02-19 19:41 ` [dpdk-dev] [PATCH 1/4] ci: remove unnecessary dependency on Linux headers David Marchand
2020-02-20 10:44 ` Thomas Monjalon
2020-02-20 14:37 ` Aaron Conole
2020-02-19 19:41 ` David Marchand [this message]
2020-02-20 11:03 ` [dpdk-dev] [PATCH 2/4] ci: fix Travis config warnings Thomas Monjalon
2020-02-20 12:09 ` David Marchand
2020-02-20 16:46 ` David Marchand
2020-02-20 21:01 ` Aaron Conole
2020-02-21 10:17 ` Thomas Monjalon
2020-02-20 14:36 ` Aaron Conole
2020-02-19 19:41 ` [dpdk-dev] [PATCH 3/4] ci: use an explicit list of Travis jobs David Marchand
2020-02-20 11:05 ` Thomas Monjalon
2020-02-20 14:35 ` Aaron Conole
2020-02-19 19:41 ` [dpdk-dev] [PATCH 4/4] ci: reorganise " David Marchand
2020-02-19 21:39 ` Aaron Conole
2020-02-20 10:42 ` Thomas Monjalon
2020-02-20 12:22 ` David Marchand
2020-02-20 14:35 ` Aaron Conole
2020-02-20 16:01 ` David Marchand
2020-02-20 19:38 ` [dpdk-dev] [dpdk-ci] " Jeremy Plsek
2020-02-20 0:18 ` [dpdk-dev] " dwilder
2020-02-20 11:07 ` Thomas Monjalon
2020-02-20 21:05 ` [dpdk-dev] [PATCH 0/4] Reorganise " 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=20200219194131.29417-3-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=maicolgabriel@hotmail.com \
--cc=thomas@monjalon.net \
/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).