From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: david.marchand@redhat.com, probb@iol.unh.edu,
Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH v2 0/2] Get fast-test suite to run on FreeBSD
Date: Fri, 20 Mar 2026 16:11:06 +0000 [thread overview]
Message-ID: <20260320161108.331745-1-bruce.richardson@intel.com> (raw)
In-Reply-To: <20260319171334.1151425-1-bruce.richardson@intel.com>
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 as issue 761.
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.
v2:
* squash patches for fixes into patch 1
* separate patch for some cleanup of process spawning into patch 2 which
does not need backport
Bruce Richardson (2):
test: fix failing tests on FreeBSD
test: simplify spawning extra test processes
app/test/process.h | 20 ++------------------
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 | 4 ++++
app/test/test_timer_secondary.c | 4 ++--
8 files changed, 29 insertions(+), 41 deletions(-)
--
2.51.0
next prev parent reply other threads:[~2026-03-20 16:11 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
2026-03-20 16:11 ` Bruce Richardson [this message]
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=20260320161108.331745-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--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