From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"aconole@redhat.com" <aconole@redhat.com>,
"maicolgabriel@hotmail.com" <maicolgabriel@hotmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Ruifeng Wang <Ruifeng.Wang@arm.com>, nd <nd@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] [RFC PATCH v1 0/2] Travis CI jobs update after credits
Date: Thu, 18 Feb 2021 07:50:23 +0000 [thread overview]
Message-ID: <7ff7c6362be44a36b7299a4a4f093784@pantheon.tech> (raw)
In-Reply-To: <DBAPR08MB58143704D0ECD8988AE6FC9098859@DBAPR08MB5814.eurprd08.prod.outlook.com>
> -----Original Message-----
> From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
> Sent: Thursday, February 18, 2021 3:40 AM
> To: Juraj Linkeš <juraj.linkes@pantheon.tech>; thomas@monjalon.net;
> david.marchand@redhat.com; aconole@redhat.com;
> maicolgabriel@hotmail.com
> Cc: dev@dpdk.org; Ruifeng Wang <Ruifeng.Wang@arm.com>; nd
> <nd@arm.com>; Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>; nd
> <nd@arm.com>
> Subject: RE: [RFC PATCH v1 0/2] Travis CI jobs update after credits
>
> <snip>
>
> > Subject: [RFC PATCH v1 0/2] Travis CI jobs update after credits
> >
> > Since Travis added credits we need to make some changes to the Travis
> > CI. Arm has a credit agreement with Travis for arm jobs, so remove x86
> > jobs. Also,
> I think there is a mis-understanding here. The credits are for the ovsrobot
> account and apply to all architectures.
>
This is likely my mistake. I thought there would only be enough credits to run just arm jobs. It seems there are enough credits to run everything, so I'll drop this patch.
> > migrate all arm jobs to the latest environment.
> >
> > Juraj Linkeš (2):
> > ci: remove x86 Travis jobs
> > ci: update arm64 Travis jobs to Graviton2
> >
> > .travis.yml | 113
> > ++++++++--------------------------------------------
> > 1 file changed, 16 insertions(+), 97 deletions(-)
> >
> > --
> > 2.20.1
next prev parent reply other threads:[~2021-02-18 7:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 9:42 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š [this message]
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
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=7ff7c6362be44a36b7299a4a4f093784@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=nd@arm.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).