From: Namhyung Kim <namhyung@kernel.org>
To: Howard Chu <howardchu95@gmail.com>
Cc: acme@kernel.org, mingo@redhat.com, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
peterz@infradead.org, kan.liang@linux.intel.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/6] perf test trace: Reduce test failures and make error messages verbose
Date: Thu, 5 Jun 2025 19:56:19 -0700 [thread overview]
Message-ID: <aEJY0xQTm1Q2cz1C@google.com> (raw)
In-Reply-To: <20250528191148.89118-1-howardchu95@gmail.com>
On Wed, May 28, 2025 at 12:11:42PM -0700, Howard Chu wrote:
> Currently, BTF tests fail constantly, this series fixes two major reasons
> why they fail, and makes the error messages acquired when using '-vv'
> more verbose, so when they fail, one can easily diagnose the problem.
>
> Before:
> $ sudo /tmp/perf test enum -vv
> 107: perf trace enum augmentation tests:
> 107: perf trace enum augmentation tests : Running
> --- start ---
> test child forked, pid 783533
> Checking if vmlinux exists
> Tracing syscall landlock_add_rule
> Tracing non-syscall tracepoint syscall
> ---- end(-1) ----
> 107: perf trace enum augmentation tests : FAILED!
>
> After:
> $ sudo /tmp/perf test enum -vv
> 107: perf trace enum augmentation tests:
> 107: perf trace enum augmentation tests : Running
> --- start ---
> test child forked, pid 851658
> Checking if vmlinux exists
> Tracing syscall landlock_add_rule
> Tracing non-syscall tracepoint timer:hrtimer_setup,timer:hrtimer_start
> [tracepoint failure] Failed to trace tracepoint timer:hrtimer_setup,timer:hrtimer_start, output:
> event syntax error: 'timer:hrtimer_setup,timer:hrtimer_start'
> \___ unknown tracepoint
>
> Error: File /sys/kernel/tracing//events/timer/hrtimer_setup not found.
> Hint: Perhaps this kernel misses some CONFIG_ setting to enable this feature?.
>
> Run 'perf list' for a list of valid events
>
> Usage: perf trace [<options>] [<command>]
> or: perf trace [<options>] -- <command> [<options>]
> or: perf trace record [<options>] [<command>]
> or: perf trace record [<options>] -- <command> [<options>]
>
> -e, --event <event> event/syscall selector. use 'perf list' to list available events---- end(-1) ----
> 107: perf trace enum augmentation tests : FAILED!
>
> Changes in v3:
> - Change the regex pattern in struct augmentation (Ian)
>
> Changes in v2:
> - Add an extra newline after error messages
> - Rename the title of patch 3 to 'Stop tracing hrtimer_setup...'
> - Take the debug diff for explanation out of patch 5 to make it apply
> normally
> - Add base-commit in this cover letter
>
> Howard Chu (6):
> perf test trace: Use shell's -f flag to check if vmlinux exists
> perf test trace: Remove set -e and print trace test's error messages
> perf test trace: Stop tracing hrtimer_setup event in trace enum test
> perf test trace: Remove set -e for BTF general tests
> perf test trace BTF: Use --sort-events in BTF general tests
> perf test trace BTF: Change the regex pattern in the struct test
Tested-by: Namhyung Kim <namhyung@kernel.org>
Thanks,
Namhyung
>
> tools/perf/tests/shell/trace_btf_enum.sh | 17 +++++++++--------
> tools/perf/tests/shell/trace_btf_general.sh | 19 +++++++++----------
> 2 files changed, 18 insertions(+), 18 deletions(-)
>
>
> base-commit: 628e124404b3db5e10e17228e680a2999018ab33
> --
> 2.45.2
>
next prev parent reply other threads:[~2025-06-06 2:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 19:11 [PATCH v3 0/6] perf test trace: Reduce test failures and make error messages verbose Howard Chu
2025-05-28 19:11 ` [PATCH v3 1/6] perf test trace: Use shell's -f flag to check if vmlinux exists Howard Chu
2025-05-28 19:11 ` [PATCH v3 2/6] perf test trace: Remove set -e and print trace test's error messages Howard Chu
2025-05-28 19:11 ` [PATCH v3 3/6] perf test trace: Stop tracing hrtimer_setup event in trace enum test Howard Chu
2025-05-28 19:11 ` [PATCH v3 4/6] perf test trace: Remove set -e for BTF general tests Howard Chu
2025-05-28 19:11 ` [PATCH v3 5/6] perf test trace BTF: Use --sort-events in " Howard Chu
2025-06-13 9:40 ` kernel test robot
2025-06-13 16:16 ` Howard Chu
2025-05-28 19:11 ` [PATCH v3 6/6] perf test trace BTF: Change the regex pattern in the struct test Howard Chu
2025-06-06 2:56 ` Namhyung Kim [this message]
2025-06-10 18:39 ` [PATCH v3 0/6] perf test trace: Reduce test failures and make error messages verbose 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=aEJY0xQTm1Q2cz1C@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=howardchu95@gmail.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--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 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.