All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2 2/2] Add a test case for perf script -F +metric
Date: Tue, 2 Jul 2024 16:00:20 -0700	[thread overview]
Message-ID: <ZoSGhJRvWEqlTKl7@google.com> (raw)
In-Reply-To: <20240628000455.1890269-2-ak@linux.intel.com>

On Thu, Jun 27, 2024 at 05:04:55PM -0700, Andi Kleen wrote:
> Just a simple test
> 
> Signed-off-by: Andi Kleen <ak@linux.intel.com>
> 
> --
> 
> v2: Avoid bashisms. Use noploop
> ---
>  tools/perf/tests/shell/script.sh | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
> diff --git a/tools/perf/tests/shell/script.sh b/tools/perf/tests/shell/script.sh
> index c1a603653662..de4b1dce55ad 100755
> --- a/tools/perf/tests/shell/script.sh
> +++ b/tools/perf/tests/shell/script.sh
> @@ -7,6 +7,7 @@ set -e
>  temp_dir=$(mktemp -d /tmp/perf-test-script.XXXXXXXXXX)
>  
>  perfdatafile="${temp_dir}/perf.data"
> +scriptoutput="${temp_dir}/script"
>  db_test="${temp_dir}/db_test.py"
>  
>  err=0
> @@ -88,8 +89,21 @@ test_parallel_perf()
>  	echo "parallel-perf test [Success]"
>  }
>  
> +test_metric()
> +{
> +	echo "script metric test"
> +	if ! perf list | grep -q cycles ; then return ; fi
> +	if ! perf list | grep -q instructions ; then return ; fi
> +	perf record -e '{cycles,instructions}' -o "${perfdatafile}" perf test -w noploop
> +	perf script -i "${perfdatafile}" -F +metric  > $scriptoutput
> +	test `grep -c metric $scriptoutput` -gt 5

The shellcheck (now part of build process) doesn't like this.

  In tests/shell/script.sh line 99:
  	test `grep -c metric $scriptoutput` -gt 5
               ^----------------------------^ SC2046 (warning): Quote this to prevent word splitting.
  
  For more information:
    https://www.shellcheck.net/wiki/SC2046 -- Quote this to prevent word splitt...
  make[4]: *** [tests/Build:91: tests/shell/script.sh.shellcheck_log] Error 1
  make[3]: *** [linux/tools/build/Makefile.build:158: tests] Error 2
  make[2]: *** [Makefile.perf:750: perf-test-in.o] Error 2
  make[2]: *** Waiting for unfinished jobs....

Thanks,
Namhyung


> +	grep metric $scriptoutput | head
> +	echo "script metric test [Success]"
> +}
> +
>  test_db
>  test_parallel_perf
> +test_metric
>  
>  cleanup
>  
> -- 
> 2.45.2
> 

  reply	other threads:[~2024-07-02 23:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28  0:04 [PATCH v2 1/2] perf script: Fix perf script -F +metric Andi Kleen
2024-06-28  0:04 ` [PATCH v2 2/2] Add a test case for " Andi Kleen
2024-07-02 23:00   ` Namhyung Kim [this message]
2024-07-02 22:58 ` [PATCH v2 1/2] perf script: Fix " Namhyung Kim

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=ZoSGhJRvWEqlTKl7@google.com \
    --to=namhyung@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=linux-perf-users@vger.kernel.org \
    /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.