From: David Gow <david@davidgow.net>
To: Mohammad abukhader <mohammad.abukhader@hotmail.com>,
"brendan.higgins@linux.dev" <brendan.higgins@linux.dev>
Cc: "raemoar63@gmail.com" <raemoar63@gmail.com>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"kunit-dev@googlegroups.com" <kunit-dev@googlegroups.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] kunit: tool: fix _list_tests filtering wrong variable when list has TAP prefix
Date: Wed, 12 Aug 2026 22:36:52 +0800 [thread overview]
Message-ID: <523c7404-6ef2-4cc2-a3b9-8ff1d0e4559d@davidgow.net> (raw)
In-Reply-To: <20260803190059.36491-1-mohammad.abukhader@hotmail.com>
Le 04/08/2026 à 3:02 AM, Mohammad abukhader a écrit :
> From: Mohammad Abu-Khader <mohammad.abukhader@hotmail.com>
>
> `_list_tests()` runs the kernel to list tests, strips printk timestamp
> lines via `extract_tap_lines()`, then drops the dummy TAP header from
> the cleaned `lines`. However the subsequent regex filter mistakenly
> operates on the original `output` instead of the cleaned `lines`. When
> the kernel output includes timestamp prefixes (common with UML or slower
> setups), e.g.:
>
> [ 0.100000] suite.test1
> [ 0.100000] suite.test2
>
> the anchored regex `^[^\s.]+\.[^\s.]+$` rejects them and `--list_tests`
> returns an empty list.
>
> Filter `lines` instead of `output`, matching the behavior of the
> adjacent `_list_tests_attr()` which already returns the cleaned list.
>
> Add a regression test with timestamp-prefixed input to verify the fix.
>
> Fixes: 723c8258c8fe ("kunit: tool: Add command line interface to filter and report attributes")
> Signed-off-by: Mohammad Abu-Khader <mohammad.abukhader@hotmail.com>
> ---
Reviewed-by: David Gow <david@davidgow.net>
Cheers,
-- David
> tools/testing/kunit/kunit.py | 2 +-
> tools/testing/kunit/kunit_tool_test.py | 12 ++++++++++++
> 2 files changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/kunit/kunit.py b/tools/testing/kunit/kunit.py
> index ac3f7159e67f..91d234ac3b57 100755
> --- a/tools/testing/kunit/kunit.py
> +++ b/tools/testing/kunit/kunit.py
> @@ -126,7 +126,7 @@ def _list_tests(linux: kunit_kernel.LinuxSourceTree, request: KunitExecRequest)
> lines.pop()
>
> # Filter out any extraneous non-test output that might have gotten mixed in.
> - return [l for l in output if re.match(r'^[^\s.]+\.[^\s.]+$', l)]
> + return [l for l in lines if re.match(r'^[^\s.]+\.[^\s.]+$', l)]
>
> def _list_tests_attr(linux: kunit_kernel.LinuxSourceTree, request: KunitExecRequest) -> Iterable[str]:
> args = ['kunit.action=list_attr']
> diff --git a/tools/testing/kunit/kunit_tool_test.py b/tools/testing/kunit/kunit_tool_test.py
> index da88c3a1651d..85ae21754bdf 100755
> --- a/tools/testing/kunit/kunit_tool_test.py
> +++ b/tools/testing/kunit/kunit_tool_test.py
> @@ -979,6 +979,18 @@ class KUnitMainTest(unittest.TestCase):
> self.linux_source_mock.run_kernel.assert_called_once_with(
> args=['kunit.action=list'], build_dir='.kunit', filter_glob='suite*', filter='', filter_action=None, timeout=300)
>
> + def test_list_tests_with_prefix(self):
> + want = ['suite.test1', 'suite.test2', 'suite2.test1']
> + self.linux_source_mock.run_kernel.return_value = [
> + '[ 0.100000] TAP version 14',
> + '[ 0.200000] suite.test1',
> + '[ 0.200000] suite.test2',
> + '[ 0.300000] suite2.test1']
> +
> + got = kunit._list_tests(self.linux_source_mock,
> + kunit.KunitExecRequest(None, None, None, False, False, '.kunit', 300, 'suite*', '', None, None, 'suite', False, False, False))
> + self.assertEqual(got, want)
> +
> @mock.patch.object(kunit, '_list_tests')
> def test_run_isolated_by_suite(self, mock_tests):
> mock_tests.return_value = ['suite.test1', 'suite.test2', 'suite2.test1']
next prev parent reply other threads:[~2026-08-12 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 16:19 [PATCH] " mohammad.abukhader
2026-07-30 12:12 ` David Gow
2026-08-03 15:56 ` Shuah Khan
2026-08-03 19:02 ` [PATCH v2] " Mohammad abukhader
2026-08-12 14:36 ` David Gow [this message]
2026-08-22 8:05 ` [PATCH v3] " Mohammad abukhader
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=523c7404-6ef2-4cc2-a3b9-8ff1d0e4559d@davidgow.net \
--to=david@davidgow.net \
--cc=brendan.higgins@linux.dev \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mohammad.abukhader@hotmail.com \
--cc=raemoar63@gmail.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®