linux.git/tools/testing/selftests/ftrace/ftracetest, branch vsnprintf

tracing/selftests: Support log output when generating KTAP output

2024-05-06T19:57:19+00:00

When -v is specified ftracetest will dump logs of test execution to the
console which if -K is also specified for KTAP output will result in
output that is not properly KTAP formatted. All that's required for KTAP
formatting is that anything we log have a '#' at the start of the line so
we can improve things by washing the output through a simple read loop.
This will help automated parsers when verbose mode is enabled.

Signed-off-by: Mark Brown 
Reviewed-by: Muhammad Usama Anjum 
Acked-by: Steven Rostedt (Google) 
Acked-by: Masami Hiramatsu (Google) 
Signed-off-by: Shuah Khan

selftest/ftrace: fix typo in ftracetest script

2024-02-20T21:47:37+00:00

Fix a typo in ftracetest script which is run when running the kselftests
for ftrace.

s/faii/fail

Signed-off-by: Kousik Sanagavarapu 
Acked-by: Masami Hiramatsu (Google) 
Signed-off-by: Shuah Khan

selftests: tracing: Fix to unmount tracefs for recovering environment

2023-09-12T15:34:20+00:00

Fix to unmount the tracefs if the ftracetest mounted it for recovering
system environment. If the tracefs is already mounted, this does nothing.

Suggested-by: Mark Brown 
Link: https://lore.kernel.org/all/29fce076-746c-4650-8358-b4e0fa215cf7@sirena.org.uk/
Fixes: cbd965bde74c ("ftrace/selftests: Return the skip code when tracing directory not configured in kernel")
Signed-off-by: Masami Hiramatsu (Google) 
Reviewed-by: Steven Rostedt (Google) 
Reviewed-by: Mark Brown 
Signed-off-by: Shuah Khan

ftrace/selftests: Add softlink to latest log directory

2023-09-11T23:06:40+00:00

When I'm debugging something with the ftrace selftests and need to look at
the logs, it becomes tedious that I need to do the following:

 ls -ltr logs
 [ copy the last directory ]
 ls logs/

to see where the logs are.

Instead, do the common practice of having a "latest" softlink to the last
run selftest. This way after running the selftest I only need to do:

 ls logs/latest/

and it will always give me the directory of the last run selftest logs!

Signed-off-by: Steven Rostedt (Google) 
Acked-by: Masami Hiramatsu (Google) 
Signed-off-by: Shuah Khan

selftests/ftace: Fix KTAP output ordering

2023-06-12T22:40:22+00:00

The KTAP parser I used to test the KTAP output for ftracetest was overly
robust and did not notice that the test number and pass/fail result were
reversed. Fix this.

Fixes: dbcf76390eb9 ("selftests/ftrace: Improve integration with kselftest runner")
Signed-off-by: Mark Brown 
Acked-by: Masami Hiramatsu (Google) 
Acked-by: Steven Rostedt (Google) 
Signed-off-by: Shuah Khan

selftests/ftrace: Improve integration with kselftest runner

2023-05-08T17:10:13+00:00

The ftrace selftests do not currently produce KTAP output, they produce a
custom format much nicer for human consumption. This means that when run in
automated test systems we just get a single result for the suite as a whole
rather than recording results for individual test cases, making it harder
to look at the test data and masking things like inappropriate skips.

Address this by adding support for KTAP output to the ftracetest script and
providing a trivial wrapper which will be invoked by the kselftest runner
to generate output in this format by default, users using ftracetest
directly will continue to get the existing output.

This is not the most elegant solution but it is simple and effective. I
did consider implementing this by post processing the existing output
format but that felt more complex and likely to result in all output being
lost if something goes seriously wrong during the run which would not be
helpful. I did also consider just writing a separate runner script but
there's enough going on with things like the signal handling for that to
seem like it would be duplicating too much.

Acked-by: Steven Rostedt (Google) 
Acked-by: Masami Hiramatsu (Google) 
Tested-by: Masami Hiramatsu (Google) 
Signed-off-by: Mark Brown 
Signed-off-by: Shuah Khan

selftests/ftrace: Stop tracing while reading the trace file by default

2021-10-27T00:27:19+00:00

Stop tracing while reading the trace file by default, to prevent
the test results while checking it and to avoid taking a long time
to check the result.
If there is any testcase which wants to test the tracing while reading
the trace file, please override this setting inside the test case.

This also recovers the pause-on-trace when clean it up.

Link: https://lkml.kernel.org/r/163529053143.690749.15365238954175942026.stgit@devnote2

Signed-off-by: Masami Hiramatsu 
Signed-off-by: Steven Rostedt (VMware)

selftests/ftrace: Support ":README" suffix for requires

2020-06-16T16:42:47+00:00

Add ":README" suffix support for the requires list, so that
the testcase can list up the required string for README file
to the requires list.

Note that the required string is treated as a fixed string,
instead of regular expression. Also, the testcase can specify
a string containing spaces with quotes. E.g.

# requires: "place: [:]":README

Signed-off-by: Masami Hiramatsu 
Reviewed-by: Tom Zanussi 
Signed-off-by: Shuah Khan

selftests/ftrace: Add "requires:" list support

2020-06-16T15:19:08+00:00

Introduce "requires:" list to check required ftrace interface
for each test. This will simplify the interface checking code
and unify the error message. Another good point is, it can
skip the ftrace initializing.

Note that this requires list must be written as a shell
comment.

Signed-off-by: Masami Hiramatsu 
Reviewed-by: Tom Zanussi 
Signed-off-by: Shuah Khan

selftests/ftrace: Allow ":" in description

2020-06-16T15:15:40+00:00

Allow ":" in the description line. Currently if there is ":"
in the test description line, the description is cut at that
point, but that was unintended.

Signed-off-by: Masami Hiramatsu 
Reviewed-by: Tom Zanussi 
Signed-off-by: Shuah Khan