From: Stephen Hemminger <stephen@networkplumber.org>
To: Marat Khalili <marat.khalili@huawei.com>
Cc: Konstantin Ananyev <konstantin.ananyev@huawei.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH] test/bpf: use unit test suite
Date: Mon, 31 Aug 2026 08:12:39 -0700 [thread overview]
Message-ID: <20260831081239.658c078d@phoenix.local> (raw)
In-Reply-To: <8ecd0e24395d4a5eb53c6c4355f73cf7@huawei.com>
On Mon, 31 Aug 2026 08:34:58 +0000
Marat Khalili <marat.khalili@huawei.com> wrote:
> Hi!
>
> > The BPF tests registered 23 separate autotests. Collapse them into a
> > single bpf_autotest suite run by unit_test_suite_runner().
>
> Some of these tests still don't pass with sanitizer enabled. With them
> registered individually there was an option to ignore these failures or only
> run the tests that are known to not contain UB. After lumping them in one suite
> running BPF tests under sanitizer is going to become much more difficult.
>
> There are other reasons why more granular tests are good, like ease of tracking
> or debugging failures. What are the benefits from collapsing them? What is the
> actual problem we are trying to solve?
The only technical difference is that meson runs individual tests in
parallel and have seen some failures on my machine.
But for me it is more about decluttering the output.
next prev parent reply other threads:[~2026-08-31 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 19:13 [PATCH] test/bpf: use unit test suite Stephen Hemminger
2026-08-31 8:34 ` Marat Khalili
2026-08-31 15:12 ` Stephen Hemminger [this message]
2026-08-31 15:47 ` Marat Khalili
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=20260831081239.658c078d@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=marat.khalili@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox