From: Namhyung Kim <namhyung@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Shuah Khan <shuahkhan@gmail.com>,
<linux-kselftest@vger.kernel.org>
Subject: Re: [RFC][PATCH] ftracetest: Fix hist unsupported result in hist selftests
Date: Tue, 24 May 2016 08:54:38 +0900 [thread overview]
Message-ID: <20160523235438.GA1636@sejong> (raw)
In-Reply-To: <20160523151538.4ea9ce0c@gandalf.local.home>
Hi Steve,
On Mon, May 23, 2016 at 03:15:38PM -0400, Steven Rostedt wrote:
>
> [ Folks, is this a proper work around? ]
>
> When histograms are not configured in the kernel, the ftracetest histogram
> selftests should return "unsupported" and not "Failed". To detect this, the
> test scripts have:
>
> FEATURE=`grep hist events/sched/sched_process_fork/trigger`
> if [ -z "$FEATURE" ]; then
> echo "hist trigger is not supported"
> exit_unsupported
> fi
>
> The problem is that '-e' is in effect and any error will cause the program
> to terminate. The grep for 'hist' fails, because it is not compiled it (thus
> unsupported), but because grep has an error code for failing to find the
> string, it causes the program to terminate, and is marked as a failed test.
We have a feature check before doing grep, doesn't it detect such
case?
if [ ! -f events/sched/sched_process_fork/trigger ]; then
echo "event trigger is not supported"
exit_unsupported
fi
Thanks,
Namhyung
>
> As a work around, I added "|| echo -n ''" to not let bash terminate the
> script on a failed grep, and then the rest of the script can handle the fact
> that histograms are not supported and return a proper result.
>
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
> ---
> tools/testing/selftests/ftrace/test.d/trigger/trigger-hist-mod.tc | 2 +-
> tools/testing/selftests/ftrace/test.d/trigger/trigger-hist.tc | 2 +-
> tools/testing/selftests/ftrace/test.d/trigger/trigger-multihist.tc | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tools/testing/selftests/ftrace/test.d/trigger/trigger-hist-mod.tc b/tools/testing/selftests/ftrace/test.d/trigger/trigger-hist-mod.tc
> index c2b61c4fda11..6c100759c758 100644
> --- a/tools/testing/selftests/ftrace/test.d/trigger/trigger-hist-mod.tc
> +++ b/tools/testing/selftests/ftrace/test.d/trigger/trigger-hist-mod.tc
> @@ -26,7 +26,7 @@ fi
> reset_tracer
> do_reset
>
> -FEATURE=`grep hist events/sched/sched_process_fork/trigger`
> +FEATURE=`grep hist events/sched/sched_process_fork/trigger || echo -n ''`
> if [ -z "$FEATURE" ]; then
> echo "hist trigger is not supported"
> exit_unsupported
> diff --git a/tools/testing/selftests/ftrace/test.d/trigger/trigger-hist.tc b/tools/testing/selftests/ftrace/test.d/trigger/trigger-hist.tc
> index b2902d42a537..8d691dc0c5cc 100644
> --- a/tools/testing/selftests/ftrace/test.d/trigger/trigger-hist.tc
> +++ b/tools/testing/selftests/ftrace/test.d/trigger/trigger-hist.tc
> @@ -26,7 +26,7 @@ fi
> reset_tracer
> do_reset
>
> -FEATURE=`grep hist events/sched/sched_process_fork/trigger`
> +FEATURE=`grep hist events/sched/sched_process_fork/trigger || echo -n ''`
> if [ -z "$FEATURE" ]; then
> echo "hist trigger is not supported"
> exit_unsupported
> diff --git a/tools/testing/selftests/ftrace/test.d/trigger/trigger-multihist.tc b/tools/testing/selftests/ftrace/test.d/trigger/trigger-multihist.tc
> index 03c4a46561fc..1a11e641e97d 100644
> --- a/tools/testing/selftests/ftrace/test.d/trigger/trigger-multihist.tc
> +++ b/tools/testing/selftests/ftrace/test.d/trigger/trigger-multihist.tc
> @@ -26,7 +26,7 @@ fi
> reset_tracer
> do_reset
>
> -FEATURE=`grep hist events/sched/sched_process_fork/trigger`
> +FEATURE=`grep hist events/sched/sched_process_fork/trigger || echo -n ''`
> if [ -z "$FEATURE" ]; then
> echo "hist trigger is not supported"
> exit_unsupported
> --
> 1.8.3.1
>
next prev parent reply other threads:[~2016-05-23 23:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 19:15 [RFC][PATCH] ftracetest: Fix hist unsupported result in hist selftests Steven Rostedt
2016-05-23 23:54 ` Namhyung Kim [this message]
2016-05-24 1:50 ` Steven Rostedt
2016-05-24 2:16 ` Namhyung Kim
2016-05-24 2:32 ` Steven Rostedt
2016-05-24 3:02 ` Namhyung Kim
2016-06-17 21:28 ` Steven Rostedt
2016-06-19 2:46 ` Masami Hiramatsu
2016-06-19 23:42 ` Namhyung Kim
2016-06-27 17:40 ` Shuah Khan
2016-06-27 17:53 ` 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=20160523235438.GA1636@sejong \
--to=namhyung@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuahkhan@gmail.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