linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Jiri Olsa <jolsa@kernel.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	David Ahern <dsahern@gmail.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Kan Liang <kan.liang@intel.com>, Andi Kleen <ak@linux.intel.com>,
	Lukasz Odzioba <lukasz.odzioba@intel.com>,
	Wang Nan <wangnan0@huawei.com>,
	lkp@01.org
Subject: Re: [lkp-robot] [perf tools]  600b7378cf: perf-sanity-tests.Share_thread_mg.fail
Date: Mon, 23 Jul 2018 08:59:10 +0200	[thread overview]
Message-ID: <20180723065910.GA7523@krava> (raw)
In-Reply-To: <20180722075323.GB23613@shao2-debian>

On Sun, Jul 22, 2018 at 03:53:24PM +0800, kernel test robot wrote:
> 
> FYI, we noticed the following commit (built with gcc-7):
> 
> commit: 600b7378cf43f522e88027874f11f63b6fbf53d8 ("[PATCH 2/4] perf tools: Add threads__get_last_match function")
> url: https://github.com/0day-ci/linux/commits/Jiri-Olsa/perf-tools-Fix-top-crashes/20180714-075809

SNIP

>   LD       plugin_function-in.o
>   LINK     plugin_function.so
>   CC       plugin_xen.o
>   LD       plugin_xen-in.o
>   LINK     plugin_xen.so
>   CC       plugin_scsi.o
>   LD       plugin_scsi-in.o
>   LINK     plugin_scsi.so
>   CC       plugin_cfg80211.o
>   LD       plugin_cfg80211-in.o
>   LINK     plugin_cfg80211.so
>   GEN      libtraceevent-dynamic-list
>   LINK     perf
>   GEN      perf-archive
>   GEN      perf-with-kcore
>   GEN      python/perf.so
> make: Leaving directory '/usr/src/linux-perf-x86_64-randconfig-s5-07160434-600b7378cf43f522e88027874f11f63b6fbf53d8/tools/perf'
> 2018-07-16 20:55:35 cd /usr/src/linux-perf-x86_64-randconfig-s5-07160434-600b7378cf43f522e88027874f11f63b6fbf53d8/tools/perf
> 2018-07-16 20:55:35 mkdir -p /pkg
> 2018-07-16 20:55:36 mkdir -p /kbuild/obj/consumer/x86_64-randconfig-s5-07160434
> 2018-07-16 20:55:36 cp /pkg/linux/x86_64-randconfig-s5-07160434/gcc-7/600b7378cf43f522e88027874f11f63b6fbf53d8/vmlinux.xz /tmp
> 2018-07-16 20:55:37 unxz -k /tmp/vmlinux.xz
> 2018-07-16 20:55:40 cp /tmp/vmlinux /kbuild/obj/consumer/x86_64-randconfig-s5-07160434
> ignored_by_lkp: BPF filter
> ignored_by_lkp: LLVM search and compile
> ignored_by_lkp: Add vfs_getname probe to get syscall args filenames
> ignored_by_lkp: Use vfs_getname probe to get syscall args filenames
> ignored_by_lkp: Check open filename arg using perf trace + vfs_getname
> ignored_by_lkp: builtin clang support
> 2018-07-16 20:55:41 sudo /usr/src/linux-perf-x86_64-randconfig-s5-07160434-600b7378cf43f522e88027874f11f63b6fbf53d8/tools/perf/perf test 1
>  1: vmlinux symtab matches kallsyms                       : Ok
> 2018-07-16 20:55:43 sudo /usr/src/linux-perf-x86_64-randconfig-s5-07160434-600b7378cf43f522e88027874f11f63b6fbf53d8/tools/perf/perf test 2
>  2: Detect openat syscall event                           : FAILED!
> 2018-07-16 20:55:43 sudo /usr/src/linux-perf-x86_64-randconfig-s5-07160434-600b7378cf43f522e88027874f11f63b6fbf53d8/tools/perf/perf test 3
>  3: Detect openat syscall event on all cpus               : FAILED!
> 2018-07-16 20:55:43 sudo /usr/src/linux-perf-x86_64-randconfig-s5-07160434-600b7378cf43f522e88027874f11f63b6fbf53d8/tools/perf/perf test 4
>  4: Read samples using the mmap interface                 : FAILED!
> 2018-07-16 20:55:43 sudo /usr/src/linux-perf-x86_64-randconfig-s5-07160434-600b7378cf43f522e88027874f11f63b6fbf53d8/tools/perf/perf test 5
>  5: Test data source output                               : Ok
> 2018-07-16 20:55:44 sudo /usr/src/linux-perf-x86_64-randconfig-s5-07160434-600b7378cf43f522e88027874f11f63b6fbf53d8/tools/perf/perf test 6
>  6: Parse event definition strings                        : FAILED!

yea, there's v2 already pulled in by Arnaldo,
that fixes this

thanks,
jirka

  reply	other threads:[~2018-07-23  6:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-12 14:20 [PATCH 0/4] perf tools: Fix top crashes Jiri Olsa
2018-07-12 14:20 ` [PATCH 1/4] perf tools: Fix struct comm_str removal crash Jiri Olsa
2018-07-15 13:08   ` Namhyung Kim
2018-07-16 10:29     ` Jiri Olsa
2018-07-17  1:49       ` Namhyung Kim
2018-07-17  9:02         ` Jiri Olsa
2018-07-18 10:44           ` Jiri Olsa
2018-07-12 14:20 ` [PATCH 2/4] perf tools: Add threads__get_last_match function Jiri Olsa
2018-07-22  7:53   ` [lkp-robot] [perf tools] 600b7378cf: perf-sanity-tests.Share_thread_mg.fail kernel test robot
2018-07-23  6:59     ` Jiri Olsa [this message]
2018-07-12 14:20 ` [PATCH 3/4] perf tools: Add threads__set_last_match function Jiri Olsa
2018-07-12 14:20 ` [PATCH 4/4] perf tools: Use last_match threads cache only in single thread mode Jiri Olsa

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=20180723065910.GA7523@krava \
    --to=jolsa@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=dsahern@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=lukasz.odzioba@intel.com \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=rong.a.chen@intel.com \
    --cc=wangnan0@huawei.com \
    /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;
as well as URLs for NNTP newsgroup(s).