[dpdk-dev] [RFC 3/3] ci: enable tests on non-arm platforms

[Aaron Conole]

Jerin Jacob Kollanukkaran <jerinj at marvell.com> writes:

>> -----Original Message-----
>> From: dev <dev-bounces at dpdk.org> On Behalf Of Aaron Conole
>> Sent: Friday, March 29, 2019 10:53 PM
>> To: dev at 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 at 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.