From: Steven Rostedt <rostedt@goodmis.org>
To: Thibault Ferrante <thibault.ferrante@canonical.com>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: shuah@kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] selftests/ftrace: Add test dependency
Date: Thu, 18 Dec 2025 18:32:26 -0500 [thread overview]
Message-ID: <20251218183226.6ada2ec0@gandalf.local.home> (raw)
In-Reply-To: <20230614105031.13543-1-thibault.ferrante@canonical.com>
On Wed, 14 Jun 2023 12:50:31 +0200
Thibault Ferrante <thibault.ferrante@canonical.com> wrote:
> test_duplicates miss a running dependency and leads to test failures
> on kernel with specific configuration.
>
Found another old patch. But this one still needs review.
Masami, does this look good to you?
-- Steve
> Signed-off-by: Thibault Ferrante <thibault.ferrante@canonical.com>
> ---
> .../testing/selftests/ftrace/test.d/dynevent/test_duplicates.tc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/ftrace/test.d/dynevent/test_duplicates.tc b/tools/testing/selftests/ftrace/test.d/dynevent/test_duplicates.tc
> index d3a79da215c8..0b5e4543e70b 100644
> --- a/tools/testing/selftests/ftrace/test.d/dynevent/test_duplicates.tc
> +++ b/tools/testing/selftests/ftrace/test.d/dynevent/test_duplicates.tc
> @@ -1,7 +1,7 @@
> #!/bin/sh
> # SPDX-License-Identifier: GPL-2.0
> # description: Generic dynamic event - check if duplicate events are caught
> -# requires: dynamic_events "e[:[<group>/][<event>]] <attached-group>.<attached-event> [<args>]":README
> +# requires: dynamic_events events/syscalls/sys_enter_openat "e[:[<group>/][<event>]] <attached-group>.<attached-event> [<args>]":README
>
> echo 0 > events/enable
>
prev parent reply other threads:[~2025-12-18 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 10:50 [PATCH] selftests/ftrace: Add test dependency Thibault Ferrante
2025-12-18 23:32 ` Steven Rostedt [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=20251218183226.6ada2ec0@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=shuah@kernel.org \
--cc=thibault.ferrante@canonical.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