public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: James Clark <james.clark@linaro.org>
Cc: Thomas Richter <tmricht@linux.ibm.com>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	acme@kernel.org, agordeev@linux.ibm.com, gor@linux.ibm.com,
	sumanthk@linux.ibm.com, hca@linux.ibm.com
Subject: Re: [PATCH] perf test: Silence perf check subcommand when not supported
Date: Wed, 25 Sep 2024 22:35:44 -0700	[thread overview]
Message-ID: <ZvTysPPKxYKjUMTA@google.com> (raw)
In-Reply-To: <f74e73b6-fa0a-4533-a9de-3c5dbc4399f3@linaro.org>

On Wed, Sep 11, 2024 at 02:34:27PM +0100, James Clark wrote:
> 
> 
> On 11/09/2024 13:28, Thomas Richter wrote:
> > Perf subcommand check might not be supported and prints an
> > error message when used:
> 
> Only in verbose mode though. Personally I don't like all the piping to
> /dev/null in the tests because I have to go and remove them every time a
> test fails, rather than just doing "-v". But as it's pretty much the pattern
> used I suppose we should continue.
> 
> > 
> >   # perf check feature -q libtraceevent
> >   perf: 'check' is not a perf-command. See 'perf --help'.
> > 
> >   Did you mean one of these?
> >          c2c
> >          sched

I think perf test is supposed to run the latest build so perf check
command should be available.  Do you see this in the test result or just
in the command line?

Thanks,
Namhyung


> >   #
> > 
> > Drop this error message, the return code is sufficient.
> > 
> > Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
> > ---
> >   tools/perf/tests/shell/lib/probe_vfs_getname.sh | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/tools/perf/tests/shell/lib/probe_vfs_getname.sh b/tools/perf/tests/shell/lib/probe_vfs_getname.sh
> > index 5c33ec7a5a63..697fbe296a62 100644
> > --- a/tools/perf/tests/shell/lib/probe_vfs_getname.sh
> > +++ b/tools/perf/tests/shell/lib/probe_vfs_getname.sh
> > @@ -32,7 +32,7 @@ skip_if_no_debuginfo() {
> >   # check if perf is compiled with libtraceevent support
> >   skip_no_probe_record_support() {
> >   	if [ $had_vfs_getname -eq 1 ] ; then
> > -		perf check feature -q libtraceevent && return 1
> > +		perf check feature -q libtraceevent >/dev/null 2>&1 && return 1
> 
> There's another of the same in tools/perf/tests/shell/test_task_analyzer.sh
> 
> With that:
> 
> Reviewed-by: James Clark <james.clark@linaro.org>

      reply	other threads:[~2024-09-26  5:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11 12:28 [PATCH] perf test: Silence perf check subcommand when not supported Thomas Richter
2024-09-11 13:34 ` James Clark
2024-09-26  5:35   ` Namhyung Kim [this message]

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=ZvTysPPKxYKjUMTA@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=james.clark@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=sumanthk@linux.ibm.com \
    --cc=tmricht@linux.ibm.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