DPDK patches and discussions
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: Juraj Linkeš <juraj.linkes@pantheon.tech>
Cc: "thomas\@monjalon.net" <thomas@monjalon.net>,
	"david.marchand\@redhat.com" <david.marchand@redhat.com>,
	"maicolgabriel\@hotmail.com" <maicolgabriel@hotmail.com>,
	"dev\@dpdk.org" <dev@dpdk.org>,
	"Ruifeng.Wang\@arm.com" <Ruifeng.Wang@arm.com>,
	"Honnappa.Nagarahalli\@arm.com" <Honnappa.Nagarahalli@arm.com>
Subject: Re: [dpdk-dev] [PATCH v2] ci: update arm64 Travis jobs to Graviton2
Date: Mon, 22 Feb 2021 14:37:32 -0500
Message-ID: <f7ty2ff3ncz.fsf@dhcp-25.97.bos.redhat.com> (raw)
In-Reply-To: <e980027180f1469e8291b8dc9071428e@pantheon.tech> ("Juraj \=\?utf-8\?Q\?Linke\=C5\=A1\=22's\?\= message of "Mon, 22 Feb 2021 14:49:17 +0000")

Juraj Linkeš <juraj.linkes@pantheon.tech> writes:

>> -----Original Message-----
>> From: Aaron Conole <aconole@redhat.com>
>> Sent: Friday, February 19, 2021 2:27 PM
>> To: Juraj Linkeš <juraj.linkes@pantheon.tech>
>> 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š <juraj.linkes@pantheon.tech> writes:
>> 
>> > 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.

>> I'm not against the change, but I don't understand it.
>> 
>> > Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
>> > ---
>> 


  reply	other threads:[~2021-02-22 19:37 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 ` [dpdk-dev] [PATCH v2] ci: update arm64 Travis jobs to Graviton2 Juraj Linkeš
2021-02-19  9:13   ` Ruifeng Wang
2021-02-19 13:27   ` Aaron Conole
2021-02-22 14:49     ` Juraj Linkeš
2021-02-22 19:37       ` Aaron Conole [this message]
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=f7ty2ff3ncz.fsf@dhcp-25.97.bos.redhat.com \
    --to=aconole@redhat.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=Ruifeng.Wang@arm.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=juraj.linkes@pantheon.tech \
    --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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git