From: Aaron Conole <aconole@redhat.com>
To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: "dev\@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC 3/3] ci: enable tests on non-arm platforms
Date: Wed, 17 Apr 2019 08:39:34 -0400 [thread overview]
Message-ID: <f7tpnpkkdq1.fsf@dhcp-25.97.bos.redhat.com> (raw)
In-Reply-To: <BYAPR18MB2424DFCD0D6025CA96557F05C8250@BYAPR18MB2424.namprd18.prod.outlook.com> (Jerin Jacob Kollanukkaran's message of "Wed, 17 Apr 2019 08:32:18 +0000")
Jerin Jacob Kollanukkaran <jerinj@marvell.com> writes:
>> -----Original Message-----
>> From: dev <dev-bounces@dpdk.org> On Behalf Of Aaron Conole
>> Sent: Friday, March 29, 2019 10:53 PM
>> To: dev@dpdk.org
>> Subject: [dpdk-dev] [RFC 3/3] ci: enable tests on non-arm platforms
>>
>> When building under Travis (or another linux CI service), enable running the tests
>> for each build.
>>
>> Signed-off-by: Aaron Conole <aconole@redhat.com>
>> ---
>> .ci/linux-build.sh | 7 +++++++
>> .ci/linux-setup.sh | 6 +++++-
>> 2 files changed, 12 insertions(+), 1 deletion(-)
>>
>> diff --git a/.ci/linux-build.sh b/.ci/linux-build.sh index 4eb7c3cf0..72510a433
>> 100755
>> --- a/.ci/linux-build.sh
>> +++ b/.ci/linux-build.sh
>> @@ -22,3 +22,10 @@ fi
>> OPTS="$OPTS --default-library=$DEF_LIB"
>> meson build --werror -Dexamples=all $OPTS ninja -C build
>> +
>> +if [ "$AARCH64" != "1" ]; then
>
> If the indention is run only on X86 then, X86 == 1 would be the correct logic as we do
> have powerpc and arm32 support in dpdk.
Correct - I should have used a more robust and targeted test.
> Any reason why we are opting out arm64?
> There are some cloud hosting services with arm64 as well.
>
> https://www.packet.com/cloud/servers/c1-large-arm/
There is At the moment, we aren't hooked up to any - do you know of one
that we can easily integrate with right now? AFAICT, there are hosting
services, but we would still need all the other things that go with CI
service (dashboards, scheduling, tracking, etc.) and it's a big project
to set up, maintain, etc.
next prev parent reply other threads:[~2019-04-17 12:39 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 17:22 [dpdk-dev] [RFC 0/3] ci: enable unit tests for non-aarch64 platforms Aaron Conole
2019-03-29 17:22 ` Aaron Conole
2019-03-29 17:22 ` [dpdk-dev] [RFC 1/3] test/meson: auto detect number of cores Aaron Conole
2019-03-29 17:22 ` Aaron Conole
2019-04-01 13:48 ` David Marchand
2019-04-01 13:48 ` David Marchand
2019-04-01 14:07 ` Aaron Conole
2019-04-01 14:07 ` Aaron Conole
2019-04-01 16:23 ` Pattan, Reshma
2019-04-01 16:23 ` Pattan, Reshma
2019-04-01 17:48 ` Aaron Conole
2019-04-01 17:48 ` Aaron Conole
2019-04-01 19:39 ` Thomas Monjalon
2019-04-01 19:39 ` Thomas Monjalon
2019-04-01 19:58 ` Aaron Conole
2019-04-01 19:58 ` Aaron Conole
2019-03-29 17:22 ` [dpdk-dev] [RFC 2/3] meson-tests: separate slower tests Aaron Conole
2019-03-29 17:22 ` Aaron Conole
2019-03-29 17:22 ` [dpdk-dev] [RFC 3/3] ci: enable tests on non-arm platforms Aaron Conole
2019-03-29 17:22 ` Aaron Conole
2019-04-17 8:32 ` Jerin Jacob Kollanukkaran
2019-04-17 8:32 ` Jerin Jacob Kollanukkaran
2019-04-17 12:39 ` Aaron Conole [this message]
2019-04-17 12:39 ` Aaron Conole
2019-04-17 15:32 ` [dpdk-dev] [EXT] " Jerin Jacob Kollanukkaran
2019-04-17 15:32 ` Jerin Jacob Kollanukkaran
2019-04-01 19:15 ` [dpdk-dev] [RFC 0/3] ci: enable unit tests for non-aarch64 platforms David Marchand
2019-04-01 19:15 ` David Marchand
2019-04-01 19:28 ` Aaron Conole
2019-04-01 19:28 ` Aaron Conole
2019-04-01 19:29 ` David Marchand
2019-04-01 19:29 ` David Marchand
2019-04-02 9:37 ` Bruce Richardson
2019-04-02 9:37 ` Bruce Richardson
2019-04-02 10:09 ` David Marchand
2019-04-02 10:09 ` David Marchand
2019-04-02 12:49 ` Aaron Conole
2019-04-02 12:49 ` Aaron Conole
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=f7tpnpkkdq1.fsf@dhcp-25.97.bos.redhat.com \
--to=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
/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).