From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, aconole@redhat.com,
Michael Santana <maicolgabriel@hotmail.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] ci: hook to GitHub Actions
Date: Mon, 14 Dec 2020 11:44:25 +0100 [thread overview]
Message-ID: <7479990.Yk6BxxKdxd@thomas> (raw)
In-Reply-To: <0da994ab-da6f-2b07-d58c-210ae1b9f1ce@intel.com>
11/12/2020 21:07, Ferruh Yigit:
> On 12/4/2020 5:36 PM, David Marchand wrote:
> > With the recent changes in terms of free access to the Travis CI, let's
> > offer an alternative with GitHub Actions.
> > Running jobs on ARM is not supported unless using external runners, so
> > this commit only adds builds for x86_64 and cross compiling for i386 and
> > aarch64.
> >
> > Differences with the Travis CI integration:
> > - Error logs are not dumped to the console when something goes wrong.
> > Instead, they are gathered in a "catch-all" step and attached as
> > artifacts.
> > - A cache entry is stored once and for all, but if no cache is found you
> > can inherit from the default branch cache. The cache is 5GB large, for
> > the whole git repository.
> > - The maximum retention of logs and artifacts is 3 months.
> > - /home/runner is world writable, so a workaround has been added for
> > starting dpdk processes.
> > - Ilya, working on OVS GHA support, noticed that jobs can run with
> > processors that don't have the same capabilities. For DPDK, this
> > impacts the ccache content since everything was built with
> > -march=native so far, and we will end up with binaries that can't run
> > in a later build. The problem has not been seen in Travis CI (?) but
> > it is safer to use a fixed "-Dmachine=default" in any case.
> > - Scheduling jobs is part of the configuration and takes the form of a
> > crontab. A build is scheduled every Monday at 0:00 (UTC) to provide a
> > default ccache for the week (useful for the ovsrobot).
> >
> > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > ---
> > Changelog since v1:
> > - changed shell variables value in CI scripts and Travis configuration
> > (s/=[^\$]*1/=\1true), this makes it easier for GHA,
> > - forced compilation as 'default' to avoid random unit tests issues in
> > GHA,
> > - scheduled a run per week on Monday at 0:00 UTC,
> > - updated the ccache key:
> > - no need to depend on the default-library parameter since this
> > parameter only impacts the linking of dpdk binaries,
> > - the week when the cache is generated is added so that jobs in
> > other branches can benefit from a recent cache (mimicking what we had
> > for the robot in Travis),
> > - realigned documentation generation with what is done in Travis:
> > generating the doc in all jobs was a waste of resources,
> >
>
> For series,
> Tested-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> Confirmed that ABI check script is detecting issues, in the absence of the
> Travis checks I am for having this alternative.
Thanks for offering an interesting CI alternative.
For the series,
Acked-by: Thomas Monjalon <thomas@monjalon.net>
next prev parent reply other threads:[~2020-12-14 10:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 21:57 [dpdk-dev] [PATCH] ci: hook to Github Actions 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
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 [this message]
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=7479990.Yk6BxxKdxd@thomas \
--to=thomas@monjalon.net \
--cc=aconole@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=maicolgabriel@hotmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.