From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: thomas@monjalon.net, david.marchand@redhat.com,
aconole@redhat.com, maicolgabriel@hotmail.com
Cc: dev@dpdk.org, Ruifeng.Wang@arm.com, Honnappa.Nagarahalli@arm.com,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>
Subject: [dpdk-dev] [PATCH v2] ci: update arm64 Travis jobs to Graviton2
Date: Fri, 19 Feb 2021 08:34:22 +0100 [thread overview]
Message-ID: <1613720062-19647-1-git-send-email-juraj.linkes@pantheon.tech> (raw)
In-Reply-To: <1613554953-14736-1-git-send-email-juraj.linkes@pantheon.tech>
Instead of using the older platform, use only the newer Graviton2
environment in Travis CI.
Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
---
.travis.yml | 26 ++++++++++++++++----------
1 file changed, 16 insertions(+), 10 deletions(-)
diff --git a/.travis.yml b/.travis.yml
index 6a2181299f..7ed982ac07 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -122,10 +122,10 @@ jobs:
- *aarch64_clang_packages
# aarch64 gcc jobs
- env: DEF_LIB="static"
- arch: arm64
- compiler: gcc
- - env: DEF_LIB="shared" RUN_TESTS=true
- arch: arm64
+ dist: focal
+ arch: arm64-graviton2
+ virt: vm
+ group: edge
compiler: gcc
- env: DEF_LIB="shared" RUN_TESTS=true
dist: focal
@@ -134,7 +134,10 @@ jobs:
group: edge
compiler: gcc
- env: DEF_LIB="shared" BUILD_DOCS=true
- arch: arm64
+ dist: focal
+ arch: arm64-graviton2
+ virt: vm
+ group: edge
compiler: gcc
addons:
apt:
@@ -142,7 +145,10 @@ jobs:
- *required_packages
- *doc_packages
- env: DEF_LIB="shared" ABI_CHECKS=true
- arch: arm64
+ dist: focal
+ arch: arm64-graviton2
+ virt: vm
+ group: edge
compiler: gcc
addons:
apt:
@@ -151,10 +157,10 @@ jobs:
- *libabigail_build_packages
# aarch64 clang jobs
- env: DEF_LIB="static"
- arch: arm64
- compiler: clang
- - env: DEF_LIB="shared" RUN_TESTS=true
- arch: arm64
+ dist: focal
+ arch: arm64-graviton2
+ virt: vm
+ group: edge
compiler: clang
- env: DEF_LIB="shared" RUN_TESTS=true
dist: focal
--
2.20.1
next prev parent reply other threads:[~2021-02-19 7:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 9:42 [dpdk-dev] [RFC PATCH v1 0/2] Travis CI jobs update after credits Juraj Linkeš
2021-02-17 9:42 ` [dpdk-dev] [RFC PATCH v1 1/2] ci: remove x86 Travis jobs Juraj Linkeš
2021-02-17 10:39 ` Thomas Monjalon
2021-02-17 15:44 ` Aaron Conole
2021-02-17 17:18 ` Honnappa Nagarahalli
2021-02-17 15:47 ` Aaron Conole
2021-02-17 17:19 ` Honnappa Nagarahalli
2021-02-17 9:42 ` [dpdk-dev] [RFC PATCH v1 2/2] ci: update arm64 Travis jobs to Graviton2 Juraj Linkeš
2021-02-17 10:43 ` [dpdk-dev] [RFC PATCH v1 0/2] Travis CI jobs update after credits Ferruh Yigit
2021-02-17 15:46 ` Aaron Conole
2021-02-17 16:08 ` Honnappa Nagarahalli
2021-02-18 2:40 ` Honnappa Nagarahalli
2021-02-18 7:50 ` Juraj Linkeš
2021-02-19 7:34 ` Juraj Linkeš [this message]
2021-02-19 9:13 ` [dpdk-dev] [PATCH v2] ci: update arm64 Travis jobs to Graviton2 Ruifeng Wang
2021-02-19 13:27 ` Aaron Conole
2021-02-22 14:49 ` Juraj Linkeš
2021-02-22 19:37 ` Aaron Conole
2021-02-23 8:28 ` [dpdk-dev] [PATCH v3] " Juraj Linkeš
2021-02-23 9:02 ` Ruifeng Wang
2021-02-23 14:38 ` Aaron Conole
2021-03-02 12:39 ` 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=1613720062-19647-1-git-send-email-juraj.linkes@pantheon.tech \
--to=juraj.linkes@pantheon.tech \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=aconole@redhat.com \
--cc=david.marchand@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).