From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH v2 2/2] perf evsel: Use evsel__name_is() helper
Date: Tue, 2 Apr 2024 22:59:36 +0800 [thread overview]
Message-ID: <202404022240.nFyJIMwC-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20240401062724.1006010-3-yangjihong@bytedance.com>
References: <20240401062724.1006010-3-yangjihong@bytedance.com>
TO: Yang Jihong <yangjihong@bytedance.com>
TO: peterz@infradead.org
TO: mingo@redhat.com
TO: acme@kernel.org
TO: namhyung@kernel.org
TO: mark.rutland@arm.com
TO: alexander.shishkin@linux.intel.com
TO: jolsa@kernel.org
TO: irogers@google.com
TO: adrian.hunter@intel.com
TO: kan.liang@linux.intel.com
TO: james.clark@arm.com
TO: linux-perf-users@vger.kernel.org
TO: linux-kernel@vger.kernel.org
CC: yangjihong@bytedance.com
Hi Yang,
kernel test robot noticed the following build errors:
[auto build test ERROR on perf-tools-next/perf-tools-next]
[also build test ERROR on tip/perf/core perf-tools/perf-tools linus/master v6.9-rc2 next-20240402]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Yang-Jihong/perf-sched-timehist-Fix-g-call-graph-option-failure/20240401-143023
base: https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git perf-tools-next
patch link: https://lore.kernel.org/r/20240401062724.1006010-3-yangjihong%40bytedance.com
patch subject: [PATCH v2 2/2] perf evsel: Use evsel__name_is() helper
:::::: branch date: 32 hours ago
:::::: commit date: 32 hours ago
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240402/202404022240.nFyJIMwC-lkp@intel.com/reproduce)
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 <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202404022240.nFyJIMwC-lkp@intel.com/
All errors (new ones prefixed by >>):
Makefile.config:1095: No libcapstone found, disables disasm engine support for 'perf script', please install libcapstone-dev/capstone-devel
Makefile.config:1160: libpfm4 not found, disables libpfm4 support. Please install libpfm4-dev
PERF_VERSION = 6.8.g91c361385eb9
builtin-trace.c: In function 'cmd_trace':
>> builtin-trace.c:4919:90: error: macro "assert" passed 2 arguments, but takes just 1
4919 | assert(evsel__name_is(trace.syscalls.events.bpf_output), "__augmented_syscalls__");
| ^
In file included from tools/include/linux/kernel.h:7,
from tools/include/linux/refcount.h:42,
from util/cgroup.h:6,
from builtin-trace.c:29:
/usr/include/assert.h:50: note: macro "assert" defined here
50 | # define assert(expr) (__ASSERT_VOID_CAST (0))
|
>> builtin-trace.c:4919:9: error: 'assert' undeclared (first use in this function)
4919 | assert(evsel__name_is(trace.syscalls.events.bpf_output), "__augmented_syscalls__");
| ^~~~~~
builtin-trace.c:915:1: note: 'assert' is defined in header '<assert.h>'; did you forget to '#include <assert.h>'?
914 | #include "trace/beauty/waitid_options.c"
+++ |+#include <assert.h>
915 |
builtin-trace.c:4919:9: note: each undeclared identifier is reported only once for each function it appears in
4919 | assert(evsel__name_is(trace.syscalls.events.bpf_output), "__augmented_syscalls__");
| ^~~~~~
make[6]: *** [tools/build/Makefile.build:105: tools/perf/builtin-trace.o] Error 1
make[6]: *** Waiting for unfinished jobs....
make[5]: *** [Makefile.perf:727: tools/perf/perf-in.o] Error 2
make[5]: *** Waiting for unfinished jobs....
make[4]: *** [Makefile.perf:264: sub-make] Error 2
make[3]: *** [Makefile:70: all] Error 2
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-04-02 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 14:59 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-01 6:27 [PATCH v2 0/2] perf sched time -g/--call-graph option & perf Yang Jihong
2024-04-01 6:27 ` [PATCH v2 2/2] perf evsel: Use evsel__name_is() helper Yang Jihong
2024-04-02 21:07 ` Arnaldo Carvalho de Melo
2024-04-02 21:10 ` 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=202404022240.nFyJIMwC-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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.