From: sashiko-bot@kernel.org
To: "Arnaldo Carvalho de Melo" <acme@kernel.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v4 16/21] perf test attr: State, spelled out in a line, why a test is skipped
Date: Fri, 16 Oct 2026 21:24:10 +0000 [thread overview]
Message-ID: <sashiko-outbox-174955@kernel.org> (raw)
In-Reply-To: <20261016212102.76550-17-acme@kernel.org>
> From: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> Per skip the default output shows a self contained one liner:
>
> unsupp 'test-record-branch-filter-any' exit 255, expected 1, no attrs recorded to verify
> skipped [kernel newer than 6.12] 'test-record-group-sampling'
> skipped [arch = !aarch64, machine = aarch64] 'test-record-graph-default'
>
> The extra notes explaining the reason, with a copy pasteable command to
> observe the failure, come in the very same stream when the verbosity is
> bumped, at -vvv, nothing is written to a separate place for later
> consultation, it is just the logging ladder:
>
> detail: '/root/bin/perf record -o /dev/null --no-bpf-event -j any kill'
> exited with 255, the expectations want the workload's 1 exit, so there
> [ ... ]
> The command suggested to observe the failure writes to /dev/null, so it
> doesn't leave a perf.data in the directory it is run from.
>
> Assisted-by: LLM
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261016212102.76550-1-acme@kernel.org?part=16
next prev parent reply other threads:[~2026-10-16 21:24 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 21:20 [PATCH v4 00/21] perf test attr: Report the failures again and cope with more than one core PMU Arnaldo Carvalho de Melo
2026-10-16 21:20 ` [PATCH v4 01/21] perf test attr: Fix record dwarf sample_type expectation Arnaldo Carvalho de Melo
2026-10-16 21:23 ` sashiko-bot
2026-10-16 21:20 ` [PATCH v4 02/21] perf python: Free the parse error entries when parsing fails Arnaldo Carvalho de Melo
2026-10-16 21:23 ` sashiko-bot
2026-10-16 21:20 ` [PATCH v4 03/21] perf test attr: Allow tests to require a core PMU Arnaldo Carvalho de Melo
2026-10-16 21:24 ` sashiko-bot
2026-10-16 21:20 ` [PATCH v4 04/21] perf test attr: Fix legacy event encodings in group tests Arnaldo Carvalho de Melo
2026-10-16 21:25 ` sashiko-bot
2026-10-16 21:20 ` [PATCH v4 05/21] perf test attr: Fix default stat metrics expectations Arnaldo Carvalho de Melo
2026-10-16 21:43 ` sashiko-bot
2026-10-16 21:20 ` [PATCH v4 06/21] perf test attr: Relax group checking for ungrouped expectations Arnaldo Carvalho de Melo
2026-10-16 21:24 ` sashiko-bot
2026-10-16 21:20 ` [PATCH v4 07/21] perf evsel: Mark the event as supported when retrying an open Arnaldo Carvalho de Melo
2026-10-16 21:25 ` sashiko-bot
2026-10-16 21:20 ` [PATCH v4 08/21] perf test attr: Ignore the core PMU type perf puts in 'config' Arnaldo Carvalho de Melo
2026-10-16 21:25 ` sashiko-bot
2026-10-16 21:20 ` [PATCH v4 09/21] perf evsel: Don't dump probe events to PERF_TEST_ATTR Arnaldo Carvalho de Melo
2026-10-16 21:23 ` sashiko-bot
2026-10-16 21:20 ` [PATCH v4 10/21] perf evsel: Close the fds opened so far when disabling missing features Arnaldo Carvalho de Melo
2026-10-16 21:24 ` sashiko-bot
2026-10-16 21:20 ` [PATCH v4 11/21] perf test attr: Introduce mask_bits(), generalizing hide_core_pmu_type() Arnaldo Carvalho de Melo
2026-10-16 21:24 ` sashiko-bot
2026-10-16 21:20 ` [PATCH v4 12/21] perf test attr: Accept either sample id bit perf asks for Arnaldo Carvalho de Melo
2026-10-16 21:24 ` sashiko-bot
2026-10-16 21:20 ` [PATCH v4 13/21] perf test attr: Ignore the dummy tracking event and the terms it carries Arnaldo Carvalho de Melo
2026-10-16 21:25 ` sashiko-bot
2026-10-16 21:20 ` [PATCH v4 14/21] perf test attr: Leave out the events of the other core PMUs Arnaldo Carvalho de Melo
2026-10-16 21:26 ` sashiko-bot
2026-10-16 21:20 ` [PATCH v4 15/21] perf test attr: Ignore the group read_format bit the PMU count can remove Arnaldo Carvalho de Melo
2026-10-16 21:24 ` sashiko-bot
2026-10-16 21:20 ` [PATCH v4 16/21] perf test attr: State, spelled out in a line, why a test is skipped Arnaldo Carvalho de Melo
2026-10-16 21:24 ` sashiko-bot [this message]
2026-10-16 21:20 ` [PATCH v4 17/21] perf tests: Introduce a 'needs_mlock' suite flag Arnaldo Carvalho de Melo
2026-10-16 21:27 ` sashiko-bot
2026-10-16 21:20 ` [PATCH v4 18/21] perf tests: Mark the C tests mapping perf ring buffers Arnaldo Carvalho de Melo
2026-10-16 21:24 ` sashiko-bot
2026-10-16 21:21 ` [PATCH v4 19/21] perf tests: Mark the shell tests not " Arnaldo Carvalho de Melo
2026-10-16 21:26 ` sashiko-bot
2026-10-16 21:21 ` [PATCH v4 20/21] perf mutex: Add a robust, process-shared mutex initializer Arnaldo Carvalho de Melo
2026-10-16 21:25 ` sashiko-bot
2026-10-16 21:21 ` [PATCH v4 21/21] perf test: Take turns using the perf mlock budget in the mmaping tests Arnaldo Carvalho de Melo
2026-10-16 21:28 ` sashiko-bot
2026-10-16 22:39 ` [PATCH v4 00/21] perf test attr: Report the failures again and cope with more than one core PMU Ian Rogers
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=sashiko-outbox-174955@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=acme@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.