From: David Marchand <david.marchand@redhat.com>
To: Aaron Conole <aconole@redhat.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
Patrick Robb <probb@iol.unh.edu>,
Anatoly Burakov <anatoly.burakov@intel.com>,
Michael Santana <maicolgabriel@hotmail.com>
Subject: Re: [RFC] ci: Add support for Cirrus-CI service to test FreeBSD.
Date: Wed, 3 Sep 2025 11:49:07 +0200 [thread overview]
Message-ID: <CAJFAV8yogQtTMPOpxJVh6mEKrtbBaKm4j-v3EN16qV2GbSqAqQ@mail.gmail.com> (raw)
In-Reply-To: <20250204160739.1603197-1-aconole@redhat.com>
On Tue, 4 Feb 2025 at 17:07, Aaron Conole <aconole@redhat.com> wrote:
>
> This commit adds preliminary support for developer driven FreeBSD testing
> via the Cirrus-CI cloud continuous integration system.
>
> NOTE: Currently, this does not successfully execute. See the following
> build result:
> https://cirrus-ci.com/task/5626189961756672
>
> Full Logs:
> https://api.cirrus-ci.com/v1/task/5626189961756672/logs/check.log
>
> The tests themselves may need to be run as root.
>
> Signed-off-by: Aaron Conole <aconole@redhat.com>
I was looking for a quick test on FreeBSD and I remembered this patch.
As long as unit tests are still in an unstable state, I would avoid
running them in the CI.
The check SPDX script should be updated to skip the new .cirrus.yml file.
Other than this, this lgtm (and works in my repo).
Thanks Aaron.
--
David Marchand
next prev parent reply other threads:[~2025-09-03 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 16:07 Aaron Conole
2025-02-04 17:33 ` Patrick Robb
2025-02-05 21:20 ` Aaron Conole
2025-02-06 20:12 ` Patrick Robb
2025-09-03 9:49 ` David Marchand [this message]
2025-09-03 9:50 ` 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=CAJFAV8yogQtTMPOpxJVh6mEKrtbBaKm4j-v3EN16qV2GbSqAqQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=maicolgabriel@hotmail.com \
--cc=probb@iol.unh.edu \
/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).