From: Marat Khalili <marat.khalili@huawei.com>
To: Stephen Hemminger <stephen@networkplumber.org>
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 15:47:26 +0000 [thread overview]
Message-ID: <9d5e7e1f3c4b4f7bb398fbb2eb429446@huawei.com> (raw)
In-Reply-To: <20260831081239.658c078d@phoenix.local>
> The only technical difference is that meson runs individual tests in
> parallel and have seen some failures on my machine.
To the best of my knowledge none of the BPF tests are timing-dependent. If they
fail to run in parallel it may very well be an issue that needs to be
investigated. If it happens again, can you save the logs and open a bug?
> But for me it is more about decluttering the output.
Hard for me to argue with this one, since it is highly subjective. But note
that for the price of 23 separate lines in the meson test output when one of
the tests actually fails the output is significantly less cluttered, only
showing the output of the relevant test.
Do you think 20+ independent tests is too much for a single library? If we set
some hard limit like this then I suppose we have to collapse them. Then I would
elevate bpf_test elements to the level of test suite cases, three levels of
containers is too much and going to be real pain to walk through in gdb.
prev parent reply other threads:[~2026-08-31 15:47 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
2026-08-31 15:47 ` Marat Khalili [this message]
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=9d5e7e1f3c4b4f7bb398fbb2eb429446@huawei.com \
--to=marat.khalili@huawei.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=stephen@networkplumber.org \
/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