All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marat Khalili <marat.khalili@huawei.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "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 11:39:11 +0000	[thread overview]
Message-ID: <68a929aed7fb4ce69e8cf81e9d09dfa7@huawei.com> (raw)
In-Reply-To: <uL3Gmts1SCa1M0sJvOuIOQ@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 don't whether it would improve, but it is a lot of tests,
> could you take this opportunity to group all BPF validation tests
> in a single registered test?
> At least it would reduce the noise in test reports.

TBH wasting many GBs of /run for no reason is a problem anyway.
I had problems with running DPDK tests in small containers after
--file-prefix became test-specific, but did not connect the dots.

I will try to merge new tests into one too if it helps test reports
(hopefully they won't exceed fast test timeout as a result).

  reply	other threads:[~2026-07-03 11:39 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 [this message]
2026-07-03 14:12   ` Stephen Hemminger

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=68a929aed7fb4ce69e8cf81e9d09dfa7@huawei.com \
    --to=marat.khalili@huawei.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.