From: David Marchand <david.marchand@redhat.com>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: "Aaron Conole" <aconole@redhat.com>, dev <dev@dpdk.org>,
"Michael Santana" <maicolgabriel@hotmail.com>,
"thomas@monjalon.net" <thomas@monjalon.net>, nd <nd@arm.com>,
"Ruifeng Wang" <Ruifeng.Wang@arm.com>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>
Subject: Re: [dpdk-dev] [PATCH] ci: hook to Github Actions
Date: Thu, 26 Nov 2020 09:06:04 +0100 [thread overview]
Message-ID: <CAJFAV8zgC9i=NK5wY3gsYKXT9MWMoQQhjhK5Vvgcc7HqXjcLqA@mail.gmail.com> (raw)
In-Reply-To: <DBAPR08MB58147600BEE239BC015DFD0E98F90@DBAPR08MB5814.eurprd08.prod.outlook.com>
On Thu, Nov 26, 2020 at 5:47 AM Honnappa Nagarahalli
<Honnappa.Nagarahalli@arm.com> wrote:
> > On Wed, Nov 25, 2020 at 2:45 PM Aaron Conole <aconole@redhat.com> wrote:
> > > Thanks for working on this. Sadly, I think we will have to abandon
> > > Travis soon - given the new changes it is looking very awful. Robot
> > > already is starved for job time.
> I am looking at [1], is DPDK not considered as open source project?
>
> [1] https://blog.travis-ci.com/oss-announcement
Ilya (@OVS) contacted the Travis support.
The reply is that a project that has sponsored contributors can not
ask for free tokens on Travis CI.
I personally did not try to contact their support given this response.
> > > Since we don't have ARM test runs, I guess we will have to rely on
> > > something else for that coverage now, but I like that there is
> > > coverage included at least to compile.
> >
> > For ARM test runs, UNH is a good candidate but nothing prevents other ARM
> > based CI from being added.
> Is it possible to keep Travis CI for Arm?
For individuals, the 10k credits with the current DPDK jobs get burned
in something like 4 runs (read: 4 runs a month).
Even if we narrow the configuration to only ARM, this will at best
give us x3, so let's say 12 runs a month.
Now consider the ovsrobot and the number of series that hit the list
on a worst^Wbest day like a week before rc1.
> > > I will need to update the robot to pull information from github
> > > actions, so for now it will need to be manually checked (but here's an
> > > example of a run:
> > > https://github.com/ovsrobot/dpdk/actions/runs/382073265). What's nice is
> > the robot is already primed to run the jobs, so that's good.
> Is there any guarantee that GitHub actions will be free forever?
There is no "forever".
At least, UNH lab which the project sponsors seems viable on the mid/long term.
--
David Marchand
next prev parent reply other threads:[~2020-11-26 8:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 21:57 David Marchand
2020-11-25 13:44 ` Aaron Conole
2020-11-25 14:31 ` David Marchand
2020-11-26 4:46 ` Honnappa Nagarahalli
2020-11-26 8:06 ` David Marchand [this message]
2020-11-26 17:01 ` Honnappa Nagarahalli
2020-12-08 14:08 ` David Marchand
2020-12-04 17:36 ` [dpdk-dev] [PATCH v2 1/2] ci: hook to GitHub Actions David Marchand
2020-12-04 17:36 ` [dpdk-dev] [PATCH v2 2/2] ci: enable v21 ABI checks David Marchand
2020-12-14 14:13 ` Aaron Conole
2020-12-11 20:07 ` [dpdk-dev] [PATCH v2 1/2] ci: hook to GitHub Actions Ferruh Yigit
2020-12-14 10:44 ` Thomas Monjalon
2020-12-14 14:12 ` Aaron Conole
2020-12-14 16:17 ` 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='CAJFAV8zgC9i=NK5wY3gsYKXT9MWMoQQhjhK5Vvgcc7HqXjcLqA@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--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).