From: Sasha Levin <sashal@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Ian Rogers <irogers@google.com>,
Kan Liang <kan.liang@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [GIT PULL] perf-tools changes for v6.13
Date: Mon, 25 Nov 2024 14:07:33 -0500 [thread overview]
Message-ID: <Z0TK9aqrQO1PremH@sashalap> (raw)
In-Reply-To: <20241125071653.1350621-1-namhyung@kernel.org>
On Sun, Nov 24, 2024 at 11:16:53PM -0800, Namhyung Kim wrote:
>Hi Linus,
>
>Please consider pulling the following changes in perf tools for v6.13.
>
>Thanks,
>Namhyung
>
>
>The following changes since commit 59b723cd2adbac2a34fc8e12c74ae26ae45bf230:
>
> Linux 6.12-rc6 (2024-11-03 14:05:52 -1000)
>
>are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools.git tags/perf-tools-for-v6.13-2024-11-24
Hey Namhyung,
After merging this PR into linus-next, the "Simple expression parser"
test has started failing:
--- start ---
test child forked, pid 292
Using CPUID GenuineIntel-6-1A-3
division by zero
syntax error
Failed to find TSC frequency in /proc/cpuinfo
FAILED tests/expr.c:250 #system_tsc_freq > 0
---- end(-1) ----
7: Simple expression parser : FAILED!
Here's a full log of the run: https://qa-reports.linaro.org/lkft/sashal-linus-next/build/v6.11-24716-gab16e9af2ff9/testrun/26045681/suite/perf/test/_7_Simple_expression_parser/log
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-11-25 19:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 7:16 [GIT PULL] perf-tools changes for v6.13 Namhyung Kim
2024-11-25 19:07 ` Sasha Levin [this message]
2024-11-26 2:53 ` Namhyung Kim
2024-11-26 7:36 ` Ian Rogers
2024-12-03 18:33 ` Namhyung Kim
2024-11-26 23:33 ` Linus Torvalds
2024-11-27 0:00 ` Namhyung Kim
2024-11-27 0:59 ` Arnaldo Carvalho de Melo
2024-11-27 3:25 ` Namhyung Kim
2024-11-27 13:12 ` Arnaldo Carvalho de Melo
2024-11-27 16:02 ` Linus Torvalds
2024-11-27 18:27 ` Namhyung Kim
2024-11-28 5:53 ` Ian Rogers
2024-11-26 23:40 ` pr-tracker-bot
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=Z0TK9aqrQO1PremH@sashalap \
--to=sashal@kernel.org \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.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