From: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ian Rogers <irogers@google.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
john.g.garry@oracle.com, Kajol Jain <kjain@linux.ibm.com>,
Ravi Bangoria <ravi.bangoria@amd.com>,
linux-perf-users@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
disgoel@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 00/17] tool/perf/test: Fix shellcheck coding/formatting issues of test shell scripts
Date: Wed, 14 Jun 2023 15:01:44 +0530 [thread overview]
Message-ID: <53B7D823-1570-4289-A632-2205EE2B522C@linux.vnet.ibm.com> (raw)
In-Reply-To: <ZIjSxwyna2ExW8JQ@kernel.org>
> On 14-Jun-2023, at 2:04 AM, Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
>
> Em Tue, Jun 13, 2023 at 10:11:28PM +0530, Athira Rajeev escreveu:
>> Patchset covers a set of fixes for coding/formatting issues observed while
>> running shellcheck tool on the perf test shell scripts. Shellcheck is a static
>> analysis tool that can find semantic/syntax bugs in the shell scripts.
>
> Thanks, applied the series.
Hi,
Thanks Arnaldo for picking up the patchset.
We will check and resubmit patch 6.
Thanks
Athira
>
> - Arnaldo
>
>> Patches 1-14 fixes the issues found with shellcheck. Patch 15, 16
>> and patch 17 address a fix in task_analyzer test.
>>
>> This cleanup is a pre-requisite to include a build option for shellcheck
>> discussed here: https://www.spinics.net/lists/linux-perf-users/msg25553.html
>> Also this is first set of patches. There will be one more set which will
>> include build option for shellcheck as discussed in the mail thread.
>>
>> Abhirup Deb (2):
>> tools/perf/tests: fix test_arm_spe.sh signal case issues
>> perf/tests/shell: fix shellscript errors for lock_contention.sh
>>
>> Aboorva Devarajan (1):
>> tools/perf/tests: Fix shellcheck issues in test_task_analyzer.sh file
>>
>> Aditya Gupta (3):
>> perf tests task_analyzer: fix bad substitution ${$1}
>> perf tests task_analyzer: print command on failure
>> perf tests task_analyzer: skip tests if no libtraceevent support
>>
>> Akanksha J N (1):
>> tools/perf/tests: Fix shellcheck warnings for
>> trace+probe_vfs_getname.sh
>>
>> Anushree Mathur (1):
>> perf/tests/shell : Shellcheck fixes for perf test
>> "test_arm_coresight.sh"
>>
>> Barnali Guha Thakurata (1):
>> tools/perf/tests/shell/stat_all_metrics: Fix shellcheck warning SC2076
>> in stat_all_metrics.sh
>>
>> Disha Goel (1):
>> tools/perf/tests: fix shellcheck warning for stat+json_output
>>
>> Geetika (1):
>> tools/perf/tests: Fix all POSIX sh warnings in perf shell test
>> test_brstack.sh
>>
>> Korrapati Likhitha (1):
>> tools/perf/tests: Fix shellcheck warnings for stat+csv_output
>>
>> Samir Mulani (1):
>> tools/perf/tests: fixed shellcheck warnings for perf shell scripts
>>
>> Shirisha G (1):
>> tools/perf/tests: fix shellcheck warnings for daemon.sh
>>
>> Sourabh Jain (1):
>> perf: get rid of unused import
>>
>> Spoorthy S (2):
>> shellcheck : fixing signal names and adding double quotes for
>> expression in test_arm_callgraph_fp
>> tools/perf/tests: Fix all POSIX sh warnings in stat+shadow_stat.sh
>>
>> .../scripts/python/arm-cs-trace-disasm.py | 1 -
>> tools/perf/tests/shell/buildid.sh | 12 +-
>> tools/perf/tests/shell/daemon.sh | 113 ++++++++++++------
>> tools/perf/tests/shell/lock_contention.sh | 70 +++++------
>> .../shell/record+probe_libc_inet_pton.sh | 6 +-
>> .../shell/record+script_probe_vfs_getname.sh | 4 +-
>> tools/perf/tests/shell/stat+csv_output.sh | 4 +-
>> tools/perf/tests/shell/stat+json_output.sh | 2 +-
>> tools/perf/tests/shell/stat+shadow_stat.sh | 4 +-
>> tools/perf/tests/shell/stat_all_metrics.sh | 6 +-
>> .../perf/tests/shell/test_arm_callgraph_fp.sh | 6 +-
>> tools/perf/tests/shell/test_arm_coresight.sh | 6 +-
>> tools/perf/tests/shell/test_arm_spe.sh | 2 +-
>> tools/perf/tests/shell/test_brstack.sh | 12 +-
>> tools/perf/tests/shell/test_task_analyzer.sh | 98 ++++++++-------
>> .../tests/shell/trace+probe_vfs_getname.sh | 6 +-
>> 16 files changed, 203 insertions(+), 149 deletions(-)
>>
>> --
>> 2.39.1
>>
>
> --
>
> - Arnaldo
prev parent reply other threads:[~2023-06-14 9:38 UTC|newest]
Thread overview: 40+ 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:04 ` Aditya Gupta
2023-06-23 18:08 ` Aditya Gupta
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
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 [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=53B7D823-1570-4289-A632-2205EE2B522C@linux.vnet.ibm.com \
--to=atrajeev@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=disgoel@linux.vnet.ibm.com \
--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=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).