public inbox for linux-trace-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>,
	Linux trace kernel <linux-trace-kernel@vger.kernel.org>,
	linux-kselftest@vger.kernel.org, Shuah Khan <shuahkhan@gmail.com>,
	Shuah Khan <skhan@linuxfoundation.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Tengda Wu <wutengda@huaweicloud.com>
Subject: Re: [PATCH] selftests/tracing: Fix false failure of subsystem event test
Date: Thu, 24 Jul 2025 09:53:09 -0400	[thread overview]
Message-ID: <20250724095309.480882c8@batman.local.home> (raw)
In-Reply-To: <20250721134212.53c3e140@batman.local.home>

Shuah,

Can you take this patch?

Thanks,

-- Steve


On Mon, 21 Jul 2025 13:42:12 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> From: Steven Rostedt <rostedt@goodmis.org>
> 
> The subsystem event test enables all "sched" events and makes sure there's
> at least 3 different events in the output. It used to cat the entire trace
> file to | wc -l, but on slow machines, that could last a very long time.
> To solve that, it was changed to just read the first 100 lines of the
> trace file. This can cause false failures as some events repeat so often,
> that the 100 lines that are examined could possibly be of only one event.
> 
> Instead, create an awk script that looks for 3 different events and will
> exit out after it finds them. This will find the 3 events the test looks
> for (eventually if it works), and still exit out after the test is
> satisfied and not cause slower machines to run forever.
> 
> Reported-by: Tengda Wu <wutengda@huaweicloud.com>
> Closes: https://lore.kernel.org/all/20250710130134.591066-1-wutengda@huaweicloud.com/
> Fixes: 1a4ea83a6e67 ("selftests/ftrace: Limit length in subsystem-enable tests")
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> ---
>  .../ftrace/test.d/event/subsystem-enable.tc   | 28 +++++++++++++++++--
>  1 file changed, 26 insertions(+), 2 deletions(-)
> 
> diff --git a/tools/testing/selftests/ftrace/test.d/event/subsystem-enable.tc b/tools/testing/selftests/ftrace/test.d/event/subsystem-enable.tc
> index b7c8f29c09a9..65916bb55dfb 100644
> --- a/tools/testing/selftests/ftrace/test.d/event/subsystem-enable.tc
> +++ b/tools/testing/selftests/ftrace/test.d/event/subsystem-enable.tc
> @@ -14,11 +14,35 @@ fail() { #msg
>      exit_fail
>  }
>  
> +# As reading trace can last forever, simply look for 3 different
> +# events then exit out of reading the file. If there's not 3 different
> +# events, then the test has failed.
> +check_unique() {
> +    cat trace | grep -v '^#' | awk '
> +	BEGIN { cnt = 0; }
> +	{
> +	    for (i = 0; i < cnt; i++) {
> +		if (event[i] == $5) {
> +		    break;
> +		}
> +	    }
> +	    if (i == cnt) {
> +		event[cnt++] = $5;
> +		if (cnt > 2) {
> +		    exit;
> +		}
> +	    }
> +	}
> +	END {
> +	    printf "%d", cnt;
> +	}'
> +}
> +
>  echo 'sched:*' > set_event
>  
>  yield
>  
> -count=`head -n 100 trace | grep -v ^# | awk '{ print $5 }' | sort -u | wc -l`
> +count=`check_unique`
>  if [ $count -lt 3 ]; then
>      fail "at least fork, exec and exit events should be recorded"
>  fi
> @@ -29,7 +53,7 @@ echo 1 > events/sched/enable
>  
>  yield
>  
> -count=`head -n 100 trace | grep -v ^# | awk '{ print $5 }' | sort -u | wc -l`
> +count=`check_unique`
>  if [ $count -lt 3 ]; then
>      fail "at least fork, exec and exit events should be recorded"
>  fi


  reply	other threads:[~2025-07-24 13:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-21 17:42 [PATCH] selftests/tracing: Fix false failure of subsystem event test Steven Rostedt
2025-07-24 13:53 ` Steven Rostedt [this message]
2025-07-24 21:53   ` Shuah Khan

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=20250724095309.480882c8@batman.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=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=shuahkhan@gmail.com \
    --cc=skhan@linuxfoundation.org \
    --cc=wutengda@huaweicloud.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