All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Ian Rogers <irogers@google.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	Namhyung Kim <namhyung@kernel.org>,
	<linux-perf-users@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linux-next:master] [perf target]  5ddf4c3a17: perf-sanity-tests.perf_record_tests.fail
Date: Wed, 25 Jun 2025 15:10:17 +0800	[thread overview]
Message-ID: <202506251422.589f230a-lkp@intel.com> (raw)



Hello,

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

commit: 5ddf4c3a17dc499fcbaf35692bc894340062dee8 ("perf target: Separate parse_uid into its own function")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master

[test failed on linux-next/master f817b6dd2b62d921a6cdc0a3ac599cd1851f343c]

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

	perf_compiler: clang
	group: group-02


config: x86_64-rhel-9.4-bpf
compiler: gcc-12
test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (Kaby 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 <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202506251422.589f230a-lkp@intel.com


2025-06-22 14:23:54 sudo /usr/src/linux-perf-x86_64-rhel-9.4-bpf-5ddf4c3a17dc499fcbaf35692bc894340062dee8/tools/perf/perf test 126 -v
126: perf record tests                                               : Running (1 active)
--- start ---
test child forked, pid 8698
 13bca6c-13bcaa5 g test_loop
perf does have symbol 'test_loop'
Basic --per-thread mode test
Per-thread record [Skipped event not supported]
Register capture test
Register capture test [Failed missing output]
Basic --system-wide mode test
System-wide record [Skipped not supported]
Basic target workload test
Workload record [Failed record]
Branch counter test
branch counter feature not supported on all core PMUs (/sys/bus/event_source/devices/cpu) [Skipped]
Cgroup sampling test
Cgroup sampling [Skipped not supported]
Basic leader sampling test
Leader sampling [Failed record]
Topdown leader sampling test
Topdown leader sampling [Skipped event parsing failed]
precise_max attribute test
precise_max attribute [Skipped no cycles:P event]
precise_max attribute [Skipped no instructions:P event]
precise_max attribute [Skipped no hardware events]
---- end(-1) ----
126: perf record tests                                               : FAILED!


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



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


             reply	other threads:[~2025-06-25  7:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-25  7:10 kernel test robot [this message]
2025-06-25 14:59 ` [linux-next:master] [perf target] 5ddf4c3a17: perf-sanity-tests.perf_record_tests.fail Ian Rogers
2025-06-25 17:36   ` 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=202506251422.589f230a-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=irogers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=lkp@intel.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 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.