public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>,
	Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: tmp.perf/core segfaulting on metrics test
Date: Fri, 2 Dec 2022 16:11:48 -0300	[thread overview]
Message-ID: <Y4pN9MbSuANbn68W@kernel.org> (raw)

While trying to get back at processing patches for Linux 6.2, what I
have at tmp.perf/core branch is failing like below, can someone try to
help in diagnosing this?

People really should try to run 'perf test' before pushing things
upstream, but maybe this is related to a recent merge with
torvalds/master, I'll check, but as a heads up and if someone wants to
help...

[root@quaco ~]# perf test 99
 99: perf all metricgroups test                                      : FAILED!
[root@quaco ~]# perf test -v 99
 99: perf all metricgroups test                                      :
--- start ---
test child forked, pid 1494614
Testing Backend

 Performance counter stats for 'system wide':

         9,978,757      CPU_CLK_UNHALTED.THREAD_ANY      #     56.7 %  tma_core_bound
/home/acme/libexec/perf-core/tests/shell/stat_all_metricgroups.sh: line 7: 1494617 Segmentation fault      (core dumped) perf stat -M "$m" -a true
test child finished with -1
---- end ----
perf all metricgroups test: FAILED!
[root@quaco ~]#


-- 

- Arnaldo

             reply	other threads:[~2022-12-02 19:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 19:11 Arnaldo Carvalho de Melo [this message]
2022-12-02 19:33 ` tmp.perf/core segfaulting on metrics test Namhyung Kim
2022-12-02 19:38   ` Namhyung Kim
2022-12-05 13:06     ` Arnaldo Carvalho de Melo
2022-12-05 13:08       ` 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=Y4pN9MbSuANbn68W@kernel.org \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.org \
    /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