From: James Clark <james.clark@arm.com>
To: Jeremy Linton <jeremy.linton@arm.com>,
linux-perf-users@vger.kernel.org,
"acme@kernel.org" <acme@kernel.org>
Cc: peterz@infradead.org, mingo@redhat.com, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
namhyung@kernel.org, irogers@google.com, leo.yan@linaro.org,
linux-kernel@vger.kernel.org, Leo Yan <leo.yan@linaro.org>
Subject: Re: [PATCH] perf tests: Fix coresight `perf test` failure.
Date: Thu, 28 Apr 2022 17:14:09 +0100 [thread overview]
Message-ID: <93e36dac-47d4-1e2b-6cb1-0092a5371810@arm.com> (raw)
In-Reply-To: <20220428151947.290146-1-jeremy.linton@arm.com>
On 28/04/2022 16:19, Jeremy Linton wrote:
> Currently the `perf test` always fails the coresight test like:
>
> 89: Check Arm CoreSight trace data recording and synthesized samples: FAILED!
>
> That is because the test_arm_coresight.sh is attempting to SIGINT the
> parent but is using $$ rather than $PPID and it sigint's itself when
> run under the perf test framework. Since this is done in a trap clause
> it ends up returning a non zero return. Since $PPID is a bash ism and
> not all distros are linking /bin/sh to bash, the alternative
> parent pid lookups are uglier than just dropping the kill, and its
> not strictly needed, lets pick the simple solution and drop the sigint.
>
> Fixes: 133fe2e617e4 ("perf tests: Improve temp file cleanup in test_arm_coresight.sh")
> Cc: James Clark <james.clark@arm.com>
> Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
> ---
> tools/perf/tests/shell/test_arm_coresight.sh | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/tools/perf/tests/shell/test_arm_coresight.sh b/tools/perf/tests/shell/test_arm_coresight.sh
> index 6de53b7ef5ff..e4cb4f1806ff 100755
> --- a/tools/perf/tests/shell/test_arm_coresight.sh
> +++ b/tools/perf/tests/shell/test_arm_coresight.sh
> @@ -29,7 +29,6 @@ cleanup_files()
> rm -f ${file}
> rm -f "${perfdata}.old"
> trap - exit term int
> - kill -2 $$
> exit $glb_err
> }
>
Reviewed-by: James Clark <james.clark@arm.com>
next prev parent reply other threads:[~2022-04-28 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 15:19 Jeremy Linton
2022-04-28 16:14 ` James Clark [this message]
2022-04-30 15:34 ` Arnaldo Carvalho de Melo
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=93e36dac-47d4-1e2b-6cb1-0092a5371810@arm.com \
--to=james.clark@arm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jeremy.linton@arm.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®