From: Bruce Richardson <bruce.richardson@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: <dev@dpdk.org>, <lylavoie@iol.unh.edu>, <probb@iol.unh.edu>
Subject: Re: [PATCH 0/7] Get fast-test suite to run on FreeBSD
Date: Fri, 20 Mar 2026 14:31:06 +0000 [thread overview]
Message-ID: <ab1aKo2xDOuIBCUm@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <CAJFAV8ynEzM+h0YTb-ONxqTcAzhu4hfj6yE0ZQFTZAi-9J02RA@mail.gmail.com>
On Fri, Mar 20, 2026 at 03:25:26PM +0100, David Marchand wrote:
> On Thu, 19 Mar 2026 at 18:13, Bruce Richardson
> <bruce.richardson@intel.com> wrote:
> >
> > Bugzilla ID: 761
> >
> > The standard "fast-tests" suite is used to sanity-check large parts
> > of the DPDK codebase, but it failed to run successfully on FreeBSD,
> > with large numbers of failures. This is a long-standing issue reported
> > in Bugzilla back in 2021 (hence the 3-digit BZ ID)
> >
> > This set attempts to rectify this situation by allowing the suite
> > to run without errors. Mostly it does this by disabling test suites
> > that rely on features like multi-process which are unsupported on
> > FreeBSD. It also fixes the test_debug suite which should run on
> > BSD but was failing.
> >
> > After this set, a run on my FreeBSD system passes with zero failures
> > and 22 tests reported as skipped.
> >
> > Bruce Richardson (7):
> > test/timer_secondary: skip test on FreeBSD
> > test/eal_flags: skip test on FreeBSD
> > test/pdump: skip test on FreeBSD
> > test/secondary_process: skip test on FreeBSD
> > test/external_memory: skip test on FreeBSD
> > test/interrupts: skip test on FreeBSD
> > test/debug: fix unit test on FreeBSD
> >
> > app/test/process.h | 11 ++++++++---
> > app/test/test_debug.c | 6 +++---
> > app/test/test_eal_flags.c | 26 +++++++++++++-------------
> > app/test/test_external_mem.c | 4 ++--
> > app/test/test_interrupts.c | 2 +-
> > app/test/test_mp_secondary.c | 4 ++--
> > app/test/test_pdump.c | 6 ++++++
> > app/test/test_timer_secondary.c | 4 ++--
> > 8 files changed, 37 insertions(+), 26 deletions(-)
>
> I would put the exec discovery rework in a first patch, then squash
> all the rest together.
> Otherwise, it lgtm on the principle.
>
Ack, will rework into a 2-patch v2.
/Bruce
next prev parent reply other threads:[~2026-03-20 14:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 17:11 [PATCH 0/7] Get fast-test suite to run on FreeBSD Bruce Richardson
2026-03-19 17:11 ` [PATCH 1/7] test/timer_secondary: skip test " Bruce Richardson
2026-03-20 14:03 ` Burakov, Anatoly
2026-03-19 17:11 ` [PATCH 2/7] test/eal_flags: " Bruce Richardson
2026-03-20 14:02 ` Burakov, Anatoly
2026-03-19 17:11 ` [PATCH 3/7] test/pdump: " Bruce Richardson
2026-03-19 17:16 ` Bruce Richardson
2026-03-21 16:14 ` Stephen Hemminger
2026-03-23 9:07 ` Bruce Richardson
2026-03-19 17:11 ` [PATCH 4/7] test/secondary_process: " Bruce Richardson
2026-03-20 14:02 ` Burakov, Anatoly
2026-03-19 17:11 ` [PATCH 5/7] test/external_memory: " Bruce Richardson
2026-03-20 14:01 ` Burakov, Anatoly
2026-03-19 17:11 ` [PATCH 6/7] test/interrupts: " Bruce Richardson
2026-03-20 14:01 ` Burakov, Anatoly
2026-03-19 17:11 ` [PATCH 7/7] test/debug: fix unit " Bruce Richardson
2026-03-20 14:00 ` Burakov, Anatoly
2026-03-20 14:02 ` David Marchand
2026-03-20 14:18 ` Bruce Richardson
2026-03-19 20:15 ` [PATCH 0/7] Get fast-test suite to run " Patrick Robb
2026-03-19 20:44 ` Patrick Robb
2026-03-20 8:33 ` Bruce Richardson
2026-03-20 14:25 ` David Marchand
2026-03-20 14:31 ` Bruce Richardson [this message]
2026-03-20 16:11 ` [PATCH v2 0/2] " Bruce Richardson
2026-03-20 16:11 ` [PATCH v2 1/2] test: fix failing tests " Bruce Richardson
2026-03-25 22:48 ` Thomas Monjalon
2026-03-20 16:11 ` [PATCH v2 2/2] test: simplify spawning extra test processes Bruce Richardson
2026-03-25 22:50 ` Thomas Monjalon
2026-03-24 16:31 ` [PATCH v2 0/2] Get fast-test suite to run on FreeBSD Adam Hassick
2026-04-08 17:44 ` [PATCH v3 " Bruce Richardson
2026-04-08 17:44 ` [PATCH v3 1/2] test: fix failing tests " Bruce Richardson
2026-04-08 17:44 ` [PATCH v3 2/2] test: simplify spawning extra test processes Bruce Richardson
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=ab1aKo2xDOuIBCUm@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=lylavoie@iol.unh.edu \
--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