From: Stephen Hemminger <stephen@networkplumber.org>
To: Marat Khalili <marat.khalili@huawei.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>,
Konstantin Ananyev <konstantin.ananyev@huawei.com>
Subject: Re: [PATCH] test/bpf: remove validation tests from CI
Date: Fri, 3 Jul 2026 07:12:44 -0700 [thread overview]
Message-ID: <20260703071244.4c6fd3c3@phoenix.local> (raw)
In-Reply-To: <2751fd1fa6d648a9b7f95797f13ef28b@huawei.com>
On Fri, 3 Jul 2026 08:48:33 +0000
Marat Khalili <marat.khalili@huawei.com> wrote:
> > The new tests for BPF validation are triggering a strange issue
> > in GitHub Action: the last tests are killed by signal 7 SIGBUS.
> >
> > The series fixing a lot of BPF issues was merged
> > but the related test has to be removed from the fast tests suite
> > which runs in some CI jobs.
> >
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
>
> I think I know the issue, it's tmpfs exhaustion. After some recent changes each
> test consumes 25MB in the --file-prefix directory independently, easily driving
> small VMs out of space. My ~30 new tests were the last drop for the CI.
>
> I will try to prepare a fix today, of course please do everything that's
> needed for the CI stability meanwhile.
The BPF tests should be using unit_test_suite_runner instead of separate tests.
That would help.
prev parent reply other threads:[~2026-07-03 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 2:27 [PATCH] test/bpf: remove validation tests from CI Thomas Monjalon
2026-07-03 8:48 ` Marat Khalili
2026-07-03 11:32 ` Thomas Monjalon
2026-07-03 11:39 ` Marat Khalili
2026-07-03 14:12 ` Stephen Hemminger [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=20260703071244.4c6fd3c3@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=marat.khalili@huawei.com \
--cc=thomas@monjalon.net \
/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