From: Samir M <samir@linux.ibm.com>
To: LKML <linux-kernel@vger.kernel.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>
Subject: [mainline]selftests/sched_ext: select_cpu_dfl_nodispatch test is failing.
Date: Mon, 13 Apr 2026 18:37:08 +0530 [thread overview]
Message-ID: <6424d036-7fab-48cb-b0df-81cd93dab781@linux.ibm.com> (raw)
Hi,
I'm reporting a test failure in the sched_ext selftests on kernel
version 7.0.0-rc7.
Test Details:
=============
Test Path: linux/tools/testing/selftests/sched_ext
Test Name: select_cpu_dfl_nodispatch
Command: ./runner -t select_cpu_dfl_nodispatch
Test Description:
================
The test is designed to verify the behavior of scx_bpf_select_cpu_dfl()
in ops.select_cpu()
Failure Details:
================
The test fails with the following output:
./runner -t select_cpu_dfl_nodispatch
===== START =====
TEST: select_cpu_dfl_nodispatch
DESCRIPTION: Verify behavior of scx_bpf_select_cpu_dfl() in ops.select_cpu()
OUTPUT:
ERR: select_cpu_dfl_nodispatch.c:53
Expected skel->bss->saw_local to be true (0)
not ok 1 select_cpu_dfl_nodispatch #
===== END =====
RESULTS:
PASSED: 0
SKIPPED: 0
FAILED: 1
Reproduction:
=============
1. Clone the upstream Linux kernel repository
2. Enable CONFIG_SCHED_CLASS_EXT in kernel configuration
3. Build and boot the kernel with sched_ext enabled
4. Navigate to linux/tools/testing/selftests/sched_ext
5. Build the selftests: make
6. Run the test: ./runner -t select_cpu_dfl_nodispatch
Environment:
============
Kernel Version: 7.0.0-rc7
Architecture: ppc64le
Could you please investigate this test failure? I'm happy to provide
additional
information or test on different configurations if needed.
If you happen to fix the above issue, then please add below tag.
Reported-by: Samir M <samir@linux.ibm.com>
Regards,
Samir.
next reply other threads:[~2026-04-13 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 13:07 Samir M [this message]
2026-04-13 15:55 ` Cheng-Yang Chou
2026-04-13 16:00 ` Cheng-Yang Chou
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=6424d036-7fab-48cb-b0df-81cd93dab781@linux.ibm.com \
--to=samir@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maddy@linux.ibm.com \
/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
all inboxes | Powered by JetHome®