From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Cc: jolsa@kernel.org, irogers@google.com, namhyung@kernel.org,
ravi.bangoria@amd.com, john.g.garry@oracle.com,
linux-perf-users@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
maddy@linux.ibm.com, kjain@linux.ibm.com,
disgoel@linux.vnet.ibm.com, Aditya Gupta <adityag@linux.ibm.com>,
Petar Gligoric <petar.gligoric@rohde-schwarz.com>,
Hagen Paul Pfeifer <hagen@jauu.net>
Subject: Re: [PATCH 16/17] perf tests task_analyzer: print command on failure
Date: Tue, 13 Jun 2023 17:07:52 -0300 [thread overview]
Message-ID: <ZIjMmKvo9QsPK+B/@kernel.org> (raw)
In-Reply-To: <20230613164145.50488-17-atrajeev@linux.vnet.ibm.com>
Em Tue, Jun 13, 2023 at 10:11:44PM +0530, Athira Rajeev escreveu:
> From: Aditya Gupta <adityag@linux.ibm.com>
>
> Instead of printing "perf command failed" everytime, print the exact
> command that run earlier
Looks like a nice improvement, added the test authors to the CC list on
this message,
Thanks, applied.
- Arnaldo
> Signed-off-by: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
> Signed-off-by: Kajol Jain <kjain@linux.ibm.com>
> Signed-off-by: Aditya Gupta <adityag@linux.ibm.com>
> ---
> tools/perf/tests/shell/test_task_analyzer.sh | 24 ++++++++++----------
> 1 file changed, 12 insertions(+), 12 deletions(-)
>
> diff --git a/tools/perf/tests/shell/test_task_analyzer.sh b/tools/perf/tests/shell/test_task_analyzer.sh
> index 84ab7e7f57d5..b094eeb3bf66 100755
> --- a/tools/perf/tests/shell/test_task_analyzer.sh
> +++ b/tools/perf/tests/shell/test_task_analyzer.sh
> @@ -53,14 +53,14 @@ prepare_perf_data() {
> test_basic() {
> out="$tmpdir/perf.out"
> perf script report task-analyzer > "$out"
> - check_exec_0 "perf"
> + check_exec_0 "perf script report task-analyzer"
> find_str_or_fail "Comm" "$out" "${FUNCNAME[0]}"
> }
>
> test_ns_rename(){
> out="$tmpdir/perf.out"
> perf script report task-analyzer --ns --rename-comms-by-tids 0:random > "$out"
> - check_exec_0 "perf"
> + check_exec_0 "perf script report task-analyzer --ns --rename-comms-by-tids 0:random"
> find_str_or_fail "Comm" "$out" "${FUNCNAME[0]}"
> }
>
> @@ -68,7 +68,7 @@ test_ms_filtertasks_highlight(){
> out="$tmpdir/perf.out"
> perf script report task-analyzer --ms --filter-tasks perf --highlight-tasks perf \
> > "$out"
> - check_exec_0 "perf"
> + check_exec_0 "perf script report task-analyzer --ms --filter-tasks perf --highlight-tasks perf"
> find_str_or_fail "Comm" "$out" "${FUNCNAME[0]}"
> }
>
> @@ -76,61 +76,61 @@ test_extended_times_timelimit_limittasks() {
> out="$tmpdir/perf.out"
> perf script report task-analyzer --extended-times --time-limit :99999 \
> --limit-to-tasks perf > "$out"
> - check_exec_0 "perf"
> + check_exec_0 "perf script report task-analyzer --extended-times --time-limit :99999 --limit-to-tasks perf"
> find_str_or_fail "Out-Out" "$out" "${FUNCNAME[0]}"
> }
>
> test_summary() {
> out="$tmpdir/perf.out"
> perf script report task-analyzer --summary > "$out"
> - check_exec_0 "perf"
> + check_exec_0 "perf script report task-analyzer --summary"
> find_str_or_fail "Summary" "$out" "${FUNCNAME[0]}"
> }
>
> test_summaryextended() {
> out="$tmpdir/perf.out"
> perf script report task-analyzer --summary-extended > "$out"
> - check_exec_0 "perf"
> + check_exec_0 "perf script report task-analyzer --summary-extended"
> find_str_or_fail "Inter Task Times" "$out" "${FUNCNAME[0]}"
> }
>
> test_summaryonly() {
> out="$tmpdir/perf.out"
> perf script report task-analyzer --summary-only > "$out"
> - check_exec_0 "perf"
> + check_exec_0 "perf script report task-analyzer --summary-only"
> find_str_or_fail "Summary" "$out" "${FUNCNAME[0]}"
> }
>
> test_extended_times_summary_ns() {
> out="$tmpdir/perf.out"
> perf script report task-analyzer --extended-times --summary --ns > "$out"
> - check_exec_0 "perf"
> + check_exec_0 "perf script report task-analyzer --extended-times --summary --ns"
> find_str_or_fail "Out-Out" "$out" "${FUNCNAME[0]}"
> find_str_or_fail "Summary" "$out" "${FUNCNAME[0]}"
> }
>
> test_csv() {
> perf script report task-analyzer --csv csv > /dev/null
> - check_exec_0 "perf"
> + check_exec_0 "perf script report task-analyzer --csv csv"
> find_str_or_fail "Comm;" csv "${FUNCNAME[0]}"
> }
>
> test_csv_extended_times() {
> perf script report task-analyzer --csv csv --extended-times > /dev/null
> - check_exec_0 "perf"
> + check_exec_0 "perf script report task-analyzer --csv csv --extended-times"
> find_str_or_fail "Out-Out;" csv "${FUNCNAME[0]}"
> }
>
> test_csvsummary() {
> perf script report task-analyzer --csv-summary csvsummary > /dev/null
> - check_exec_0 "perf"
> + check_exec_0 "perf script report task-analyzer --csv-summary csvsummary"
> find_str_or_fail "Comm;" csvsummary "${FUNCNAME[0]}"
> }
>
> test_csvsummary_extended() {
> perf script report task-analyzer --csv-summary csvsummary --summary-extended \
> >/dev/null
> - check_exec_0 "perf"
> + check_exec_0 "perf script report task-analyzer --csv-summary csvsummary --summary-extended"
> find_str_or_fail "Out-Out;" csvsummary "${FUNCNAME[0]}"
> }
>
> --
> 2.39.1
>
--
- Arnaldo
next prev parent reply other threads:[~2023-06-13 20:08 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 16:41 [PATCH 00/17] tool/perf/test: Fix shellcheck coding/formatting issues of test shell scripts Athira Rajeev
2023-06-13 16:41 ` [PATCH 01/17] perf: get rid of unused import Athira Rajeev
2023-06-13 19:54 ` Arnaldo Carvalho de Melo
2023-06-14 1:59 ` Leo Yan
2023-06-14 2:34 ` Arnaldo Carvalho de Melo
2023-06-14 2:48 ` Leo Yan
2023-06-13 16:41 ` [PATCH 02/17] tools/perf/tests: fix shellcheck warning for stat+json_output Athira Rajeev
2023-06-13 16:41 ` [PATCH 03/17] shellcheck : fixing signal names and adding double quotes for expression in test_arm_callgraph_fp Athira Rajeev
2023-06-13 16:41 ` [PATCH 04/17] tools/perf/tests: fix shellcheck warnings for daemon.sh Athira Rajeev
2023-06-13 16:41 ` [PATCH 05/17] tools/perf/tests: Fix shellcheck warnings for stat+csv_output Athira Rajeev
2023-06-13 16:41 ` [PATCH 06/17] tools/perf/tests: Fix shellcheck warnings for trace+probe_vfs_getname.sh Athira Rajeev
2023-06-14 2:21 ` Arnaldo Carvalho de Melo
2023-06-13 16:41 ` [PATCH 07/17] perf/tests/shell : Shellcheck fixes for perf test "test_arm_coresight.sh" Athira Rajeev
2023-06-13 16:41 ` [PATCH 08/17] tools/perf/tests/shell/stat_all_metrics: Fix shellcheck warning SC2076 in stat_all_metrics.sh Athira Rajeev
2023-06-13 16:41 ` [PATCH 09/17] tools/perf/tests: Fix shellcheck issues in test_task_analyzer.sh file Athira Rajeev
2023-06-13 16:41 ` [PATCH 10/17] tools/perf/tests: fix test_arm_spe.sh signal case issues Athira Rajeev
2023-06-13 16:41 ` [PATCH 11/17] perf/tests/shell: fix shellscript errors for lock_contention.sh Athira Rajeev
2023-06-13 16:41 ` [PATCH 12/17] tools/perf/tests: fixed shellcheck warnings for perf shell scripts Athira Rajeev
2023-06-13 16:41 ` [PATCH 13/17] tools/perf/tests: Fix all POSIX sh warnings in perf shell test test_brstack.sh Athira Rajeev
2023-06-13 16:41 ` [PATCH 14/17] tools/perf/tests: Fix all POSIX sh warnings in stat+shadow_stat.sh Athira Rajeev
2023-06-13 16:41 ` [PATCH 15/17] perf tests task_analyzer: fix bad substitution ${$1} Athira Rajeev
2023-06-13 20:06 ` Arnaldo Carvalho de Melo
2023-06-21 0:48 ` Namhyung Kim
2023-06-21 10:03 ` Aditya Gupta
2023-06-21 15:23 ` Namhyung Kim
2023-06-21 18:43 ` Aditya Gupta
2023-06-22 21:33 ` Namhyung Kim
2023-06-22 23:25 ` Namhyung Kim
2023-06-23 18:19 ` Aditya Gupta
2023-06-23 23:11 ` Namhyung Kim
2023-06-13 16:41 ` [PATCH 16/17] perf tests task_analyzer: print command on failure Athira Rajeev
2023-06-13 20:07 ` Arnaldo Carvalho de Melo [this message]
2023-06-13 20:43 ` Hagen Paul Pfeifer
2023-06-13 16:41 ` [PATCH 17/17] perf tests task_analyzer: skip tests if no libtraceevent support Athira Rajeev
2023-07-13 1:16 ` Ian Rogers
2023-07-13 8:35 ` Aditya Gupta
2023-06-13 20:34 ` [PATCH 00/17] tool/perf/test: Fix shellcheck coding/formatting issues of test shell scripts Arnaldo Carvalho de Melo
2023-06-14 9:31 ` Athira Rajeev
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=ZIjMmKvo9QsPK+B/@kernel.org \
--to=acme@kernel.org \
--cc=adityag@linux.ibm.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=disgoel@linux.vnet.ibm.com \
--cc=hagen@jauu.net \
--cc=irogers@google.com \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=kjain@linux.ibm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=namhyung@kernel.org \
--cc=petar.gligoric@rohde-schwarz.com \
--cc=ravi.bangoria@amd.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;
as well as URLs for NNTP newsgroup(s).