From: Mark Brown <broonie@kernel.org>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Namhyung Kim <namhyung@kernel.org>
Cc: James Clark <james.clark@linaro.org>, Leo Yan <leo.yan@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the perf tree
Date: Mon, 19 Jan 2026 16:09:44 +0000 [thread overview]
Message-ID: <aW5XSAo88_LBPSYI@sirena.org.uk> (raw)
Hi all,
After merging the perf tree, today's linux-next build (arm64 perf)
failed like this:
Exception processing /tmp/next/perf/pmu-events/arch/arm64/arm/cortex-a510/pmu.json
Traceback (most recent call last):
File "/tmp/next/build/tools/perf/pmu-events/jevents.py", line 1405, in ftw
action(parents, item)
~~~~~~^^^^^^^^^^^^^^^
File "/tmp/next/build/tools/perf/pmu-events/jevents.py", line 656, in preprocess_one_file
for event in read_json_events(item.path, topic):
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^
File "/tmp/next/build/tools/perf/pmu-events/jevents.py", line 464, in read_json_events
events = json.load(open(path), object_hook=JsonEvent)
File "/usr/lib/python3.13/json/__init__.py", line 293, in load
return loads(fp.read(),
cls=cls, object_hook=object_hook,
parse_float=parse_float, parse_int=parse_int,
parse_constant=parse_constant, object_pairs_hook=object_pairs_hook, **kw)
File "/usr/lib/python3.13/json/__init__.py", line 359, in loads
return cls(**kw).decode(s)
~~~~~~~~~~~~~~~~^^^
File "/usr/lib/python3.13/json/decoder.py", line 345, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.13/json/decoder.py", line 361, in raw_decode
obj, end = self.scan_once(s, idx)
~~~~~~~~~~~~~~^^^^^^^^
File "/tmp/next/build/tools/perf/pmu-events/jevents.py", line 422, in __init__
raise argparse.ArgumentTypeError('Cannot find arch std event:', arch_std)
argparse.ArgumentTypeError: ('Cannot find arch std event:', 'PMU_OVFS')
Caused by commit
a66f6242fbf52 (perf vendor events arm64: Remove uncountable events)
I have used the perf tree from 20260116 instead.
next reply other threads:[~2026-01-19 16:09 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 16:09 Mark Brown [this message]
2026-01-19 16:37 ` linux-next: build failure after merge of the perf tree James Clark
2026-01-19 16:43 ` Mark Brown
2026-01-19 16:55 ` James Clark
2026-01-19 17:02 ` Mark Brown
2026-01-26 15:13 ` Mark Brown
2026-01-26 15:20 ` James Clark
-- strict thread matches above, loose matches on Subject: below --
2025-03-26 23:22 Stephen Rothwell
2025-03-28 6:40 ` Namhyung Kim
2025-02-14 4:20 Stephen Rothwell
2025-01-09 23:05 Stephen Rothwell
2025-01-09 23:31 ` Charlie Jenkins
2025-01-10 14:01 ` Arnaldo Carvalho de Melo
2025-01-10 17:32 ` Arnaldo Carvalho de Melo
2025-01-10 18:59 ` Charlie Jenkins
2025-01-10 19:22 ` Charlie Jenkins
2024-10-10 23:23 Stephen Rothwell
2024-09-05 1:55 Stephen Rothwell
2024-04-01 22:41 Stephen Rothwell
2024-04-02 20:17 ` Arnaldo Carvalho de Melo
2024-04-12 15:22 ` Arnaldo Carvalho de Melo
2024-04-13 2:43 ` Stephen Rothwell
2024-03-21 21:41 Stephen Rothwell
2024-03-21 23:18 ` Arnaldo Carvalho de Melo
2024-03-21 23:19 ` Arnaldo Carvalho de Melo
2024-03-21 23:32 ` Stephen Rothwell
2024-03-22 2:13 ` Stephen Rothwell
2024-03-22 14:32 ` Arnaldo Carvalho de Melo
2024-03-21 23:36 ` Stephen Rothwell
2024-03-21 23:40 ` arnaldo.melo
2024-03-21 23:48 ` Arnaldo Carvalho de Melo
2024-02-21 23:06 Stephen Rothwell
2024-02-23 19:50 ` Arnaldo Carvalho de Melo
2024-02-06 23:40 Stephen Rothwell
2024-02-07 0:02 ` Ian Rogers
2023-10-24 23:26 Stephen Rothwell
2023-10-25 0:34 ` Namhyung Kim
2023-05-29 23:05 Stephen Rothwell
2023-05-30 2:16 ` Ian Rogers
2023-03-16 22:50 Stephen Rothwell
2023-03-16 23:11 ` Arnaldo Carvalho de Melo
2023-03-16 23:55 ` Stephen Rothwell
2023-03-17 3:23 ` Ian Rogers
2023-03-21 21:39 ` Stephen Rothwell
2023-03-22 18:37 ` Ian Rogers
2023-03-22 22:54 ` Stephen Rothwell
2023-03-23 13:27 ` Arnaldo Carvalho de Melo
2023-03-27 20:31 ` Ian Rogers
2023-03-28 1:33 ` Stephen Rothwell
2023-03-28 19:47 ` Arnaldo Carvalho de Melo
2023-03-28 23:06 ` Stephen Rothwell
2023-03-29 12:28 ` Arnaldo Carvalho de Melo
2023-04-03 5:15 ` Stephen Rothwell
2022-08-30 22:34 Stephen Rothwell
2022-09-01 5:11 ` Anshuman Khandual
2022-09-06 19:05 ` Stephen Rothwell
2022-09-07 2:31 ` Anshuman Khandual
2022-09-07 3:00 ` Stephen Rothwell
2022-09-07 4:22 ` Anshuman Khandual
2022-09-08 15:21 ` Arnaldo Carvalho de Melo
2022-07-20 23:05 Stephen Rothwell
2022-07-21 2:35 ` Ian Rogers
2022-07-21 3:55 ` Stephen Rothwell
2022-07-21 5:33 ` Ian Rogers
2022-01-05 22:19 Stephen Rothwell
2022-01-07 8:58 ` kajoljain
2022-01-11 21:45 ` Stephen Rothwell
2022-01-11 22:01 ` Arnaldo Carvalho de Melo
2022-01-12 5:30 ` kajoljain
2022-01-12 6:16 ` Stephen Rothwell
2022-01-14 12:03 ` Michael Ellerman
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=aW5XSAo88_LBPSYI@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=james.clark@linaro.org \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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