From: mhiramat at kernel.org (Masami Hiramatsu)
Subject: [PATCH 09/24] selftests: ftrace: return Kselftest Skip code for skipped tests
Date: Tue, 8 May 2018 12:29:09 +0900 [thread overview]
Message-ID: <20180508122909.e64612790be5a62cefbf1476@kernel.org> (raw)
In-Reply-To: <20180507111721.7f8a6b35@gandalf.local.home>
On Mon, 7 May 2018 11:17:21 -0400
Steven Rostedt <rostedt at goodmis.org> wrote:
> On Fri, 4 May 2018 19:13:13 -0600
> "Shuah Khan (Samsung OSG)" <shuah at kernel.org> wrote:
>
> > When ftrace test is skipped because of unmet dependencies and/or
> > unsupported configuration, it returns 0 which is treated as a pass
> > by the Kselftest framework. This leads to false positive result even
> > when the test could not be run.
> >
> > Change it to return kselftest skip code when a test gets skipped to
> > clearly report that the test could not be run.
> >
> > Kselftest framework SKIP code is 4 and the framework prints appropriate
> > messages to indicate that the test is skipped.
> >
>
> I'm fine with this change, but I believe Masami and perhaps others
> have scripts that expect zero return.
Oh, I'm happy with updating my script to follow the kselftest
framework spec, since that is the standard.
Shuah, is there any document which describe the return code for
kselftest framework? (And I think it should report some FAIL/PASS counts
to kselftest
However, this patch seems not working as you expected.
If kselftest framework would like to get the SKIP code from ftrace script,
you need to update TOTAL_RESULT before leave.
> If anything, we probably need to have a way to override the ksft_skip
> via a command line argument.
>
> Masami?
Agreed. Maybe we can pass the option via an environment variable.
Thanks,
>
> -- Steve
>
> > Signed-off-by: Shuah Khan (Samsung OSG) <shuah at kernel.org>
> > ---
> > tools/testing/selftests/ftrace/ftracetest | 8 ++++++--
> > 1 file changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/tools/testing/selftests/ftrace/ftracetest b/tools/testing/selftests/ftrace/ftracetest
> > index f9a9d424c980..b731c8cdcffb 100755
> > --- a/tools/testing/selftests/ftrace/ftracetest
> > +++ b/tools/testing/selftests/ftrace/ftracetest
> > @@ -23,6 +23,9 @@ echo " If <dir> is -, all logs output in console only"
> > exit $1
> > }
> >
> > +# Kselftest framework requirement - SKIP code is 4.
> > +ksft_skip=4
> > +
> > errexit() { # message
> > echo "Error: $1" 1>&2
> > exit 1
> > @@ -30,7 +33,8 @@ errexit() { # message
> >
> > # Ensuring user privilege
> > if [ `id -u` -ne 0 ]; then
> > - errexit "this must be run by root user"
> > + echo "Skipping: test must be run by root user"
> > + exit $ksft_skip
> > fi
> >
> > # Utilities
> > @@ -249,7 +253,7 @@ trap 'SIG_RESULT=$UNTESTED' $SIG_UNTESTED
> > SIG_UNSUPPORTED=$((SIG_BASE + UNSUPPORTED))
> > exit_unsupported () {
> > kill -s $SIG_UNSUPPORTED $SIG_PID
> > - exit 0
> > + exit $ksft_skip
> > }
> > trap 'SIG_RESULT=$UNSUPPORTED' $SIG_UNSUPPORTED
> >
>
--
Masami Hiramatsu <mhiramat at kernel.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: mhiramat@kernel.org (Masami Hiramatsu)
Subject: [PATCH 09/24] selftests: ftrace: return Kselftest Skip code for skipped tests
Date: Tue, 8 May 2018 12:29:09 +0900 [thread overview]
Message-ID: <20180508122909.e64612790be5a62cefbf1476@kernel.org> (raw)
Message-ID: <20180508032909.gng9CbyVyksDFh451z6TEPnDJXZThalpw5JuDSO8Lwk@z> (raw)
In-Reply-To: <20180507111721.7f8a6b35@gandalf.local.home>
On Mon, 7 May 2018 11:17:21 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Fri, 4 May 2018 19:13:13 -0600
> "Shuah Khan (Samsung OSG)" <shuah@kernel.org> wrote:
>
> > When ftrace test is skipped because of unmet dependencies and/or
> > unsupported configuration, it returns 0 which is treated as a pass
> > by the Kselftest framework. This leads to false positive result even
> > when the test could not be run.
> >
> > Change it to return kselftest skip code when a test gets skipped to
> > clearly report that the test could not be run.
> >
> > Kselftest framework SKIP code is 4 and the framework prints appropriate
> > messages to indicate that the test is skipped.
> >
>
> I'm fine with this change, but I believe Masami and perhaps others
> have scripts that expect zero return.
Oh, I'm happy with updating my script to follow the kselftest
framework spec, since that is the standard.
Shuah, is there any document which describe the return code for
kselftest framework? (And I think it should report some FAIL/PASS counts
to kselftest
However, this patch seems not working as you expected.
If kselftest framework would like to get the SKIP code from ftrace script,
you need to update TOTAL_RESULT before leave.
> If anything, we probably need to have a way to override the ksft_skip
> via a command line argument.
>
> Masami?
Agreed. Maybe we can pass the option via an environment variable.
Thanks,
>
> -- Steve
>
> > Signed-off-by: Shuah Khan (Samsung OSG) <shuah at kernel.org>
> > ---
> > tools/testing/selftests/ftrace/ftracetest | 8 ++++++--
> > 1 file changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/tools/testing/selftests/ftrace/ftracetest b/tools/testing/selftests/ftrace/ftracetest
> > index f9a9d424c980..b731c8cdcffb 100755
> > --- a/tools/testing/selftests/ftrace/ftracetest
> > +++ b/tools/testing/selftests/ftrace/ftracetest
> > @@ -23,6 +23,9 @@ echo " If <dir> is -, all logs output in console only"
> > exit $1
> > }
> >
> > +# Kselftest framework requirement - SKIP code is 4.
> > +ksft_skip=4
> > +
> > errexit() { # message
> > echo "Error: $1" 1>&2
> > exit 1
> > @@ -30,7 +33,8 @@ errexit() { # message
> >
> > # Ensuring user privilege
> > if [ `id -u` -ne 0 ]; then
> > - errexit "this must be run by root user"
> > + echo "Skipping: test must be run by root user"
> > + exit $ksft_skip
> > fi
> >
> > # Utilities
> > @@ -249,7 +253,7 @@ trap 'SIG_RESULT=$UNTESTED' $SIG_UNTESTED
> > SIG_UNSUPPORTED=$((SIG_BASE + UNSUPPORTED))
> > exit_unsupported () {
> > kill -s $SIG_UNSUPPORTED $SIG_PID
> > - exit 0
> > + exit $ksft_skip
> > }
> > trap 'SIG_RESULT=$UNSUPPORTED' $SIG_UNSUPPORTED
> >
>
--
Masami Hiramatsu <mhiramat at kernel.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Shuah Khan (Samsung OSG)" <shuah@kernel.org>,
mhiramat@kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 09/24] selftests: ftrace: return Kselftest Skip code for skipped tests
Date: Tue, 8 May 2018 12:29:09 +0900 [thread overview]
Message-ID: <20180508122909.e64612790be5a62cefbf1476@kernel.org> (raw)
In-Reply-To: <20180507111721.7f8a6b35@gandalf.local.home>
On Mon, 7 May 2018 11:17:21 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Fri, 4 May 2018 19:13:13 -0600
> "Shuah Khan (Samsung OSG)" <shuah@kernel.org> wrote:
>
> > When ftrace test is skipped because of unmet dependencies and/or
> > unsupported configuration, it returns 0 which is treated as a pass
> > by the Kselftest framework. This leads to false positive result even
> > when the test could not be run.
> >
> > Change it to return kselftest skip code when a test gets skipped to
> > clearly report that the test could not be run.
> >
> > Kselftest framework SKIP code is 4 and the framework prints appropriate
> > messages to indicate that the test is skipped.
> >
>
> I'm fine with this change, but I believe Masami and perhaps others
> have scripts that expect zero return.
Oh, I'm happy with updating my script to follow the kselftest
framework spec, since that is the standard.
Shuah, is there any document which describe the return code for
kselftest framework? (And I think it should report some FAIL/PASS counts
to kselftest
However, this patch seems not working as you expected.
If kselftest framework would like to get the SKIP code from ftrace script,
you need to update TOTAL_RESULT before leave.
> If anything, we probably need to have a way to override the ksft_skip
> via a command line argument.
>
> Masami?
Agreed. Maybe we can pass the option via an environment variable.
Thanks,
>
> -- Steve
>
> > Signed-off-by: Shuah Khan (Samsung OSG) <shuah@kernel.org>
> > ---
> > tools/testing/selftests/ftrace/ftracetest | 8 ++++++--
> > 1 file changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/tools/testing/selftests/ftrace/ftracetest b/tools/testing/selftests/ftrace/ftracetest
> > index f9a9d424c980..b731c8cdcffb 100755
> > --- a/tools/testing/selftests/ftrace/ftracetest
> > +++ b/tools/testing/selftests/ftrace/ftracetest
> > @@ -23,6 +23,9 @@ echo " If <dir> is -, all logs output in console only"
> > exit $1
> > }
> >
> > +# Kselftest framework requirement - SKIP code is 4.
> > +ksft_skip=4
> > +
> > errexit() { # message
> > echo "Error: $1" 1>&2
> > exit 1
> > @@ -30,7 +33,8 @@ errexit() { # message
> >
> > # Ensuring user privilege
> > if [ `id -u` -ne 0 ]; then
> > - errexit "this must be run by root user"
> > + echo "Skipping: test must be run by root user"
> > + exit $ksft_skip
> > fi
> >
> > # Utilities
> > @@ -249,7 +253,7 @@ trap 'SIG_RESULT=$UNTESTED' $SIG_UNTESTED
> > SIG_UNSUPPORTED=$((SIG_BASE + UNSUPPORTED))
> > exit_unsupported () {
> > kill -s $SIG_UNSUPPORTED $SIG_PID
> > - exit 0
> > + exit $ksft_skip
> > }
> > trap 'SIG_RESULT=$UNSUPPORTED' $SIG_UNSUPPORTED
> >
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2018-05-08 3:29 UTC|newest]
Thread overview: 123+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 1:13 [PATCH 01/24] selftests: android: ion: return Kselftest Skip code for skipped tests shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` [PATCH 02/24] selftests: breakpoints: " shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` [PATCH 03/24] selftests: cpu-hotplug: " shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` [PATCH 04/24] selftests: cpufreq: " shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-07 5:01 ` viresh.kumar
2018-05-07 5:01 ` Viresh Kumar
2018-05-07 5:01 ` Viresh Kumar
2018-05-05 1:13 ` [PATCH 05/24] selftests: efivarfs: " shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` [PATCH 06/24] selftests: exec: " shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-08 0:03 ` smuckle.linux
2018-05-08 0:03 ` Steve Muckle
2018-05-08 0:03 ` Steve Muckle
2018-05-05 1:13 ` [PATCH 07/24] selftests: filesystems: " shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-06 8:15 ` christian.brauner
2018-05-06 8:15 ` Christian Brauner
2018-05-06 8:15 ` Christian Brauner
2018-05-05 1:13 ` [PATCH 08/24] selftests: firmware: " shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-09 19:27 ` mcgrof
2018-05-09 19:27 ` Luis R. Rodriguez
2018-05-09 19:27 ` Luis R. Rodriguez
2018-05-05 1:13 ` [PATCH 09/24] selftests: ftrace: " shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-07 15:17 ` rostedt
2018-05-07 15:17 ` Steven Rostedt
2018-05-07 15:17 ` Steven Rostedt
2018-05-08 3:29 ` mhiramat [this message]
2018-05-08 3:29 ` Masami Hiramatsu
2018-05-08 3:29 ` Masami Hiramatsu
2018-05-08 3:38 ` mhiramat
2018-05-08 3:38 ` Masami Hiramatsu
2018-05-08 3:38 ` Masami Hiramatsu
2018-05-10 20:18 ` shuah
2018-05-10 20:18 ` Shuah Khan
2018-05-10 20:18 ` Shuah Khan
2018-05-11 6:09 ` mhiramat
2018-05-11 6:09 ` Masami Hiramatsu
2018-05-11 6:09 ` Masami Hiramatsu
2018-05-05 1:13 ` [PATCH 10/24] selftests: gpio: " Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` shuah
2018-05-05 1:13 ` [PATCH 11/24] selftests: intel_pstate: " shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` [PATCH 12/24] selftests: ipc: " shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` [PATCH 13/24] selftests: kmod: " shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-09 19:28 ` mcgrof
2018-05-09 19:28 ` Luis R. Rodriguez
2018-05-09 19:28 ` Luis R. Rodriguez
2018-05-05 1:13 ` [PATCH 14/24] selftests: kvm: " shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-07 11:46 ` pbonzini
2018-05-07 11:46 ` Paolo Bonzini
2018-05-07 11:46 ` Paolo Bonzini
2018-05-07 19:41 ` shuah
2018-05-07 19:41 ` Shuah Khan
2018-05-07 19:41 ` Shuah Khan
2018-05-07 20:19 ` shuah
2018-05-07 20:19 ` Shuah Khan
2018-05-07 20:19 ` Shuah Khan
2018-05-05 1:13 ` [PATCH 15/24] selftests: lib: add prime_numbers.sh test to Makefile shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` [PATCH 16/24] selftests: lib: return Kselftest Skip code for skipped tests shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` [PATCH 17/24] selftests: locking: add Makefile for locking test shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` [PATCH 18/24] selftests: locking: return Kselftest Skip code for skipped tests shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` [PATCH 19/24] selftests: media_tests: " shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` [PATCH 20/24] selftests: membarrier: " shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` [PATCH 21/24] selftests: memfd: " shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:52 ` mike.kravetz
2018-05-05 1:52 ` Mike Kravetz
2018-05-05 1:52 ` Mike Kravetz
2018-05-07 18:45 ` shuah
2018-05-07 18:45 ` Shuah Khan
2018-05-07 18:45 ` Shuah Khan
2018-05-07 21:16 ` shuah
2018-05-07 21:16 ` Shuah Khan
2018-05-07 21:16 ` Shuah Khan
2018-05-05 1:13 ` [PATCH 22/24] selftests: memory-hotplug: " shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` [PATCH 23/24] selftests: mqueue: " shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` [PATCH 24/24] selftests: net: " shuah
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-05 1:13 ` Shuah Khan (Samsung OSG)
2018-05-07 11:04 ` [PATCH 01/24] selftests: android: ion: " pintu.ping
2018-05-07 11:04 ` Pintu Kumar
2018-05-07 11:04 ` Pintu Kumar
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=20180508122909.e64612790be5a62cefbf1476@kernel.org \
--to=unknown@example.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.