From: Mikael Beckius via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Subject: [lttng-dev] [PATCH] Fix incorrect number of tests in test_callstack
Date: Thu, 20 Oct 2022 19:12:26 +0200 [thread overview]
Message-ID: <20221020171226.3450-1-mikael.beckius@windriver.com> (raw)
regression/kernel/test_callstack (Wstat: 256 Tests: 12 Failed: 1)
Failed test: 12
Non-zero exit status: 1
Parse errors: Bad plan. You planned 11 tests but ran 12.
Signed-off-by: Mikael Beckius <mikael.beckius@windriver.com>
---
tests/regression/kernel/test_callstack | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/regression/kernel/test_callstack b/tests/regression/kernel/test_callstack
index a4477fd7c..b5d604535 100755
--- a/tests/regression/kernel/test_callstack
+++ b/tests/regression/kernel/test_callstack
@@ -9,7 +9,7 @@ TEST_DESC="Kernel tracer - Callstack context"
CURDIR=$(dirname "$0")/
TESTDIR=$CURDIR/../..
-NUM_TESTS=11
+NUM_TESTS=12
TEST_APP_USERSPACE="$TESTDIR/utils/testapp/gen-syscall-events-callstack/gen-syscall-events-callstack"
TEST_APP_KERNELSPACE="$TESTDIR/utils/testapp/gen-syscall-events/gen-syscall-events"
PARSE_CALLSTACK="$TESTDIR/utils/parse-callstack.py"
@@ -123,7 +123,7 @@ function test_kernel_callstack()
# Only run userspace callstack test on x86
uname -m | grep -E "x86" >/dev/null 2>&1
if test $? == 0; then
- NUM_TESTS=$((NUM_TESTS+11))
+ NUM_TESTS=$((NUM_TESTS+10))
RUN_USERSPACE_TEST=1
else
RUN_USERSPACE_TEST=0
--
2.34.1
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next reply other threads:[~2022-10-21 14:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 17:12 Mikael Beckius via lttng-dev [this message]
2022-10-21 18:38 ` Jérémie Galarneau via lttng-dev
2022-10-24 8:08 ` Beckius, Mikael via lttng-dev
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=20221020171226.3450-1-mikael.beckius@windriver.com \
--to=lttng-dev@lists.lttng.org \
--cc=mikael.beckius@windriver.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