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 stat] faebee18d7: perf-sanity-tests.perf_stat_CSV_output_linter.fail
Date: Thu, 31 Jul 2025 15:12:29 +0800 [thread overview]
Message-ID: <202507310835.8b83968c-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "perf-sanity-tests.perf_stat_CSV_output_linter.fail" on:
commit: faebee18d720d9e209946ece3e468c06cf13f5ec ("perf stat: Move metric list from config to evlist")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 0b90c3b6d76ea512dc3dac8fb30215e175b0019a]
in testcase: perf-sanity-tests
version:
with following parameters:
perf_compiler: gcc
group: group-01
config: x86_64-rhel-9.4-bpf
compiler: gcc-12
test machine: 224 threads 2 sockets Intel(R) Xeon(R) Platinum 8480+ (Sapphire Rapids) with 256G 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/202507310835.8b83968c-lkp@intel.com
2025-07-27 19:30:58 sudo /usr/src/linux-perf-x86_64-rhel-9.4-bpf-faebee18d720d9e209946ece3e468c06cf13f5ec/tools/perf/perf test 94 -v
94: perf stat CSV output linter : Running (1 active)
--- start ---
test child forked, pid 12625
Checking CSV output: no args wrong number of fields. expected 6 in @1252940@100.00@9.4@% tma_backend_bound
---- end(-1) ----
94: perf stat CSV output linter : FAILED!
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250731/202507310835.8b83968c-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-07-31 7:12 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=202507310835.8b83968c-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.