From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Michael Petlan <mpetlan@redhat.com>
Cc: linux-perf-users@vger.kernel.org, irogers@google.com,
namhyung@kernel.org, acme@redhat.com
Subject: Re: [PATCH 2/2] perf test attr: Fix wrong size expectation for events
Date: Tue, 6 Oct 2026 17:26:48 +0200 [thread overview]
Message-ID: <asUTODqjJUH5MwSE@x2> (raw)
In-Reply-To: <asT4xQW9Vy492Yyl@x2>
On Tue, Oct 06, 2026 at 03:33:57PM +0200, Arnaldo Carvalho de Melo wrote:
> The test is still failing tho, for some other reason:
> running '/home/acme/libexec/perf-core/tests/shell/attr/test-record-graph-default'
> test limitation '!aarch64'
> excluded architecture list ['aarch64']
> running '/home/acme/libexec/perf-core/tests/shell/attr/test-record-graph-default-aarch64'
> test limitation 'aarch64'
> skipped [x86_64] '/home/acme/libexec/perf-core/tests/shell/attr/test-record-graph-default-aarch64'
> running '/home/acme/libexec/perf-core/tests/shell/attr/test-record-graph-dwarf'
> expected sample_type=45359, got 12583
> FAILED '/home/acme/libexec/perf-core/tests/shell/attr/test-record-graph-dwarf' - match failure
> ---- end(-1) ----
> 82: Perf attribute expectations test : FAILED!
Some fixes for problems undetected because of the lack of error
propagation:
⬢ [acme@tb-x2-perf perf-tools-next]$ git log --oneline -5
027108ff3952e8ae (HEAD -> perf-tools-next) perf test attr: Fix legacy event encodings in group tests
12d947c0d8e7aac6 perf test attr: Fix record dwarf sample_type expectation
cec590f3de003895 perf test attr: Fix wrong size expectation for events
04a0a19ede01e771 perf test attr: Propagate the return value from the test to the wrapper
1dc462fc21490767 (perf-tools-next.korg/tmp.perf-tools-next, perf-tools-next.korg/perf-tools-next, five/perf-tools-next, acme.korg/tmp.perf-tools-next, acme.korg/perf-tools-next) perf test: Add a test for perf timechart --tui
⬢ [acme@tb-x2-perf perf-tools-next]$
Still working to see all gets fixed and that test passes again.
- Arnado
next prev parent reply other threads:[~2026-10-06 15:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 22:30 [PATCH 0/2] perf test attr: Fix and re-enable the test Michael Petlan
2026-09-24 22:30 ` [PATCH 1/2] perf test attr: Propagate the return value from the test to the wrapper Michael Petlan
2026-09-24 22:32 ` sashiko-bot
2026-09-24 22:30 ` [PATCH 2/2] perf test attr: Fix wrong size expectation for events Michael Petlan
2026-09-24 22:34 ` sashiko-bot
2026-10-06 13:33 ` Arnaldo Carvalho de Melo
2026-10-06 15:26 ` Arnaldo Carvalho de Melo [this message]
2026-10-05 22:47 ` [PATCH 0/2] perf test attr: Fix and re-enable the test Namhyung Kim
2026-10-06 13:13 ` 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=asUTODqjJUH5MwSE@x2 \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=irogers@google.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mpetlan@redhat.com \
--cc=namhyung@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.