mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <yi1.lai@intel.com>
To: Michael Petlan <mpetlan@redhat.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
	linux-kernel@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	linux-perf-users@vger.kernel.org, yi1.lai@intel.com
Subject: [linus:master] [perf test attr]  f8596112cb: perf-sanity-tests.Perf_attribute_expectations_test.fail
Date: Mon, 2 Nov 2026 11:03:57 +0800	[thread overview]
Message-ID: <202611020206.eb217e49-lkp@intel.com> (raw)


Hello,

kernel test robot noticed "perf-sanity-tests.Perf_attribute_expectations_test.fail" on:

commit: f8596112cbad0072cdc957c0ea06695afda246dc ("perf test attr: Propagate the return value from the test to the wrapper") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master

[test failed on linux-next/master 7649ba73f9e7e1e04d0b46213e39c79ae09dd55c]

Note: this commit is very likely not the root cause, but rather the change that makes the pre-existing failure visible. This Commit correctly propagates the return value, so the test-record-branch-filter-any_call mismatch on this machine is now surfaced.

in testcase: perf-sanity-tests
with following parameters:

	perf_compiler: clang
	group: group-02


config: x86_64-rhel-9.4-bpf
compiler: gcc-14
test machine: 16 threads Intel(R) Core(TM) i7-13620H (Raptor Lake) with 32G memory

(please refer to attached dmesg/kmsg for entire log/backtrace)


If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <yi1.lai@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202611020206.eb217e49-lkp@intel.com


2026-10-31 15:26:58 sudo ASAN_OPTIONS=fast_unwind_on_malloc=0 /usr/src/linux-perf-x86_64-rhel-9.4-bpf-f8596112cbad0072cdc957c0ea06695afda246dc/tools/perf/perf test 82 -v
 82: Perf attribute expectations test                                                                          : Running (1 active)
---- start ----
...
expected mmap=1, got 0
expected comm=1, got 0
expected freq=1, got 0
expected enable_on_exec=1, got 0
expected task=1, got 0
expected sample_id_all=1, got 0
expected branch_sample_type=16, got 0
FAILED '/usr/src/perf_selftests-x86_64-rhel-9.4-bpf-f8596112cbad0072cdc957c0ea06695afda246dc/tools/perf/tests/shell/attr/test-record-branch-filter-any_call' - match failure
---- end(-1) ----
 82: Perf attribute expectations test                                                                          : FAILED!

=== Test Summary ===
Passed main tests : 0
Passed subtests   : 0
Skipped tests     : 0
Failed tests      : 1
List of failed tests:
   82: Perf attribute expectations test


The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20261102/202611020206.eb217e49-lkp@intel.com



--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki



                 reply	other threads:[~2026-11-02  3:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202611020206.eb217e49-lkp@intel.com \
    --to=yi1.lai@intel.com \
    --cc=acme@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mpetlan@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=oe-lkp@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 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®