Juraj Linkeš [off-list ref] writes:

quoted

-----Original Message-----
From: Aaron Conole <aconole@redhat.com>
Sent: Friday, February 19, 2021 2:27 PM
To: Juraj Linkeš <redacted>
Cc: thomas@monjalon.net; david.marchand@redhat.com;
maicolgabriel@hotmail.com; dev@dpdk.org; Ruifeng.Wang@arm.com;
Honnappa.Nagarahalli@arm.com
Subject: Re: [PATCH v2] ci: update arm64 Travis jobs to Graviton2

Juraj Linkeš [off-list ref] writes:

quoted

Instead of using the older platform, use only the newer Graviton2
environment in Travis CI.

Can you expand on this a bit.  Why should we need to use the newer
environment?  What problems will occur by using the older environment?

We're seeing intermittent issues with the environment.

An example run https://travis-ci.com/github/ovsrobot/dpdk/builds/217641063

Issue 1:
collect2: fatal error: ld terminated with signal 9 [Killed]

This suggest an issue with resources.

Issue 2:
ticketlock_autotest sometimes times out. This could be due variable
resource availability in a container environment, but may not be.

There could be other issues, I haven't analysed all of the logs, but
there are enough to make us want to switch to Graviton2 for all jobs.

We're don't see either issue with the Graviton2 environment (which uses VMs).

I guess it would be good to mention this motivation in the commit
message - otherwise looking at the history we won't understand why we
made this change.

Please post v2 mentioning resource availability issues with travis-ci
using the container infrastructure which don't seem to impact the VM
infrastructure.  I will ACK.

quoted

I'm not against the change, but I don't understand it.

quoted

Signed-off-by: Juraj Linkeš <redacted>
---