public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alexis Lothoré" <alexis.lothore@bootlin.com>
To: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>,
	"Alexis Lothoré" <alexis.lothore@bootlin.com>
Cc: "bpf" <bpf@vger.kernel.org>,
	"open list:KERNEL SELFTEST FRAMEWORK"
	<linux-kselftest@vger.kernel.org>,
	"Quentin Monnet" <qmo@kernel.org>,
	"Bastien Curutchet (eBPF Foundation)"
	<bastien.curutchet@bootlin.com>
Subject: Re: [Question] json parsing and bpf selftests dependencies
Date: Fri, 27 Feb 2026 08:31:34 +0100	[thread overview]
Message-ID: <DGPKHPMDRQXL.3ARKDNHT1FB4O@bootlin.com> (raw)
In-Reply-To: <CAADnVQKM3zCvUv_ja+QCCO20eHZ0qrYpReNguXToZpaf46vEFg@mail.gmail.com>

On Thu Feb 26, 2026 at 6:21 PM CET, Alexei Starovoitov wrote:
> On Thu, Feb 26, 2026 at 2:36 AM Alexis Lothoré
> <alexis.lothore@bootlin.com> wrote:
>>
>> Hello,
>> I am pursuing my quest to convert standalone bpf tests (from
>> tools/testing/selftests/bpf) into the test_progs framework so they can
>> be executed automatically by the CI tooling.
>>
>> I would like to continue on the bpftool tests, especially
>> test_bpftool.py ([1]).
>
> I think it outlived itself long ago.
> Just delete it.
> Any new bpftool features can be tested through test_progs.
> No need to test json output specifically.
> It's diminishing returns.

Ok. That's a doubt I had while converting the first round of tests
(bpf_metadata, bpftool_map_access), whether we really want to test exact
bpftool CLI output, or if test_progs->libbpf testing was fine.

I'll remote this test_bpftool.py then, thanks for the feedback.

Alexis

-- 
Alexis Lothoré, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


      reply	other threads:[~2026-02-27  7:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26 10:32 [Question] json parsing and bpf selftests dependencies Alexis Lothoré
2026-02-26 15:01 ` Mykyta Yatsenko
2026-02-26 17:21 ` Alexei Starovoitov
2026-02-27  7:31   ` Alexis Lothoré [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=DGPKHPMDRQXL.3ARKDNHT1FB4O@bootlin.com \
    --to=alexis.lothore@bootlin.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=bastien.curutchet@bootlin.com \
    --cc=bpf@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=qmo@kernel.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