From: Crystal Wood <crwood@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-kernel@vger.kernel.org,
John Kacur <jkacur@redhat.com>, Tomas Glozar <tglozar@redhat.com>,
Costa Shulyupin <costa.shul@redhat.com>,
Crystal Wood <crwood@redhat.com>
Subject: [PATCH v2 6/7] tools/rtla: Add test engine support for unexpected output
Date: Sat, 6 Sep 2025 21:23:24 -0500 [thread overview]
Message-ID: <20250907022325.243930-7-crwood@redhat.com> (raw)
In-Reply-To: <20250907022325.243930-1-crwood@redhat.com>
Add a check() parameter to indicate which text must not appear in the
output.
Simplify the code so that we can print failures as they happen rather
than trying to figure out what went wrong after printing "not ok". This
also means that "not ok" gets printed after the info rather than before,
which seems more intuitive anyway.
Signed-off-by: Crystal Wood <crwood@redhat.com>
---
v2: Preserved the original ordering of "not ok" versus diagnostics as per
convention
---
tools/tracing/rtla/tests/engine.sh | 26 ++++++++++++++++++--------
1 file changed, 18 insertions(+), 8 deletions(-)
diff --git a/tools/tracing/rtla/tests/engine.sh b/tools/tracing/rtla/tests/engine.sh
index a97d644ead99..c7de3d6ed6a8 100644
--- a/tools/tracing/rtla/tests/engine.sh
+++ b/tools/tracing/rtla/tests/engine.sh
@@ -43,6 +43,7 @@ check() {
tested_command=$1
expected_exitcode=${3:-0}
expected_output=$4
+ unexpected_output=$5
# Simple check: run rtla with given arguments and test exit code.
# If TEST_COUNT is set, run the test. Otherwise, just count.
ctr=$(($ctr + 1))
@@ -53,24 +54,33 @@ check() {
# Run rtla; in case of failure, include its output as comment
# in the test results.
result=$(eval stdbuf -oL $TIMEOUT "$RTLA" $2 2>&1); exitcode=$?
+ failbuf=''
+ fail=0
+
# Test if the results matches if requested
- if [ -n "$expected_output" ]
+ if [ -n "$expected_output" ] && ! grep -qE "$expected_output" <<< "$result"
then
- grep -E "$expected_output" <<< "$result" > /dev/null; grep_result=$?
- else
- grep_result=0
+ fail=1
+ failbuf+=$(printf "# Output match failed: \"%s\"" "$expected_output")
+ failbuf+=$'\n'
fi
- if [ $exitcode -eq $expected_exitcode ] && [ $grep_result -eq 0 ]
+ if [ -n "$unexpected_output" ] && grep -qE "$unexpected_output" <<< "$result"
+ then
+ fail=1
+ failbuf+=$(printf "# Output non-match failed: \"%s\"" "$unexpected_output")
+ failbuf+=$'\n'
+ fi
+
+ if [ $exitcode -eq $expected_exitcode ] && [ $fail -eq 0 ]
then
echo "ok $ctr - $1"
else
- echo "not ok $ctr - $1"
# Add rtla output and exit code as comments in case of failure
+ echo "not ok $ctr - $1"
+ echo -n "$failbuf"
echo "$result" | col -b | while read line; do echo "# $line"; done
printf "#\n# exit code %s\n" $exitcode
- [ -n "$expected_output" ] && [ $grep_result -ne 0 ] && \
- printf "# Output match failed: \"%s\"\n" "$expected_output"
fi
fi
}
--
2.48.1
next prev parent reply other threads:[~2025-09-07 2:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 2:23 [PATCH v2 0/7] tools/rtla: Code consolidation and osnoise actions Crystal Wood
2025-09-07 2:23 ` [PATCH v2 1/7] tools/rtla: Consolidate common parameters into shared structure Crystal Wood
2025-09-07 2:23 ` [PATCH v2 2/7] tools/rtla: Move top/hist params into common struct Crystal Wood
2025-09-07 2:23 ` [PATCH v2 3/7] tools/rtla: Create common_apply_config() Crystal Wood
2025-09-07 2:23 ` [PATCH v2 4/7] tools/rtla: Consolidate code between osnoise/timerlat and hist/top Crystal Wood
2025-09-07 19:51 ` Costa Shulyupin
2025-09-08 13:53 ` Costa Shulyupin
2025-09-07 2:23 ` [PATCH v2 5/7] tools/rtla: Fix -A option name in test comment Crystal Wood
2025-09-07 2:23 ` Crystal Wood [this message]
2025-09-08 14:48 ` [PATCH v2 6/7] tools/rtla: Add test engine support for unexpected output Crystal Wood
2025-09-07 2:23 ` [PATCH v2 7/7] tools/rtla: Add remaining support for osnoise actions Crystal Wood
2025-09-09 11:25 ` [PATCH v2 0/7] tools/rtla: Code consolidation and " Tomas Glozar
2025-09-26 14:19 ` Tomas Glozar
2025-09-27 8:44 ` Steven Rostedt
2025-09-27 9:47 ` Steven Rostedt
2025-09-27 10:09 ` Steven Rostedt
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=20250907022325.243930-7-crwood@redhat.com \
--to=crwood@redhat.com \
--cc=costa.shul@redhat.com \
--cc=jkacur@redhat.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglozar@redhat.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