The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Sean Young <sean@mess.org>
To: Bastien Curutchet <bastien.curutchet@bootlin.com>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
	Andrii Nakryiko <andrii@kernel.org>,
	Eduard Zingerman <eddyz87@gmail.com>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Martin KaFai Lau <martin.lau@linux.dev>,
	Kumar Kartikeya Dwivedi <memxor@gmail.com>,
	Song Liu <song@kernel.org>,
	Yonghong Song <yonghong.song@linux.dev>,
	Jiri Olsa <jolsa@kernel.org>, Shuah Khan <shuah@kernel.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Alexis Lothore <alexis.lothore@bootlin.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"open list:KERNEL SELFTEST FRAMEWORK"
	<linux-kselftest@vger.kernel.org>, bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH bpf-next] bpf/selftests: remove lirc test
Date: Wed, 1 Jul 2026 17:41:26 +0100	[thread overview]
Message-ID: <akVDNsud-Z9DXmem@extorris.mess.org> (raw)
In-Reply-To: <8419863d-1e0f-4343-acca-ad75c66092cf@bootlin.com>

Hi Bastien,

On Wed, Jul 01, 2026 at 05:26:20PM +0200, Bastien Curutchet wrote:
> On 6/8/26 2:51 PM, Bastien Curutchet wrote:
> > On 6/5/26 5:21 PM, Sean Young wrote:
> > > On Fri, Jun 05, 2026 at 06:39:51AM -0700, Alexei Starovoitov wrote:
> > > > On Fri, Jun 5, 2026 at 12:58 AM Bastien Curutchet (eBPF Foundation)
> > > > <bastien.curutchet@bootlin.com> wrote:
> > > > > 
> > > > > test_lirc_mode.sh fails with the following when run from the vmtest VM:
> > > > > root@(none):/root/bpf# ./test_lirc_mode2.sh
> > > > > Failed to read decoded IR: Resource temporarily unavailable
> > > > > FAIL: lirc_mode2
> > > > > 
> > > > > As part of the ongoing effort to get rid of any standalone test, this
> > > > > script should either be fixed and converted to test_progs or removed.
> > > > > 
> > > > > Remove it.
> > > > 
> > > > cc Sean
> > > 
> > > I've sent a fix to for the test in a separate email.
> > > 
> > > This regressed a long time ago; is anyone running these tests? There is
> > > not much point to selftests if they're not run by anyone. I should add
> > > them to linux-media CI, but is anyone in bpf running them?
> > > 
> > > I am not familiar with test_progs, what's that?
> > > 
> > test_progs is the selftest's application run by the BPF CI for every
> > patch series sent to bpf@vger.kernel.org (or PR done to the BPF github).
> > It's made out of the C files located in tools/testing/selftests/bpf/
> > prog_tests/.
> > 
> > The shell scripts under tools/testing/selftests/bpf aren't run
> > automatically anywhere (to my knowledge at least). The goal of the 'on-
> > going effort' I mentioned is to get rid of these scripts by either
> > integrating them to the 'test_progs infra' or removing them.
> > 
> > If you're going to add this script to the linux-media CI, maybe we could
> > remove it from here ?
> > 
> > 
> Gentle ping: would it be OK for you if we remove the test from here ? I've
> seen your fix, the bug was introduced in 5.17, which means no one had run it
> for 4 years. Given that, I'm not sure it's worth the effort of porting it to
> the test_progs infra.

So the test is useful and should be run regularly. It should be ported to
test_progs or moved to media-ci. I haven't decided yet which way I want to
go. I'm just a bit busy right now, I'll get round to it soon.

Thanks,

Sean 

      reply	other threads:[~2026-07-01 16:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-05  7:58 [PATCH bpf-next] bpf/selftests: remove lirc test Bastien Curutchet (eBPF Foundation)
2026-06-05 13:39 ` Alexei Starovoitov
2026-06-05 15:21   ` Sean Young
2026-06-08 12:51     ` Bastien Curutchet
2026-07-01 15:26       ` Bastien Curutchet
2026-07-01 16:41         ` Sean Young [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=akVDNsud-Z9DXmem@extorris.mess.org \
    --to=sean@mess.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=alexis.lothore@bootlin.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bastien.curutchet@bootlin.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yonghong.song@linux.dev \
    /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