From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [paulmck-rcu:dev.2026.09.02a] BUILD REGRESSION 02d3dbb63ea80cac75734d77309015f13d5e73c9
Date: Sat, 05 Sep 2026 13:54:57 +0800 [thread overview]
Message-ID: <202609051355.F1T2qXnd-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2026.09.02a
branch HEAD: 02d3dbb63ea80cac75734d77309015f13d5e73c9 rcutorture: Disable RCU priority boost testing on non-TREE03 scenarios
Unverified Error/Warning (likely false positive, kindly check if interested):
kernel/rcu/hazptrtorture.c:465:1: internal compiler error: in final_scan_insn_1, at final.cc:2823
Error/Warning ids grouped by kconfigs:
recent_errors
`-- csky-allmodconfig
`-- kernel-rcu-hazptrtorture.c:internal-compiler-error:in-final_scan_insn_1-at-final.cc
elapsed time: 2128m
configs tested: 22
configs skipped: 0
tested configs:
alpha allnoconfig gcc-16.1.0
arc allnoconfig gcc-16.1.0
arm allnoconfig clang-17
arm64 allnoconfig gcc-16.1.0
csky allnoconfig gcc-16.1.0
hexagon allnoconfig clang-24
i386 allnoconfig gcc-14
loongarch allnoconfig clang-20
m68k allnoconfig gcc-16.1.0
microblaze allnoconfig gcc-16.1.0
mips allnoconfig gcc-16.1.0
nios2 allnoconfig gcc-11.5.0
openrisc allnoconfig gcc-16.1.0
parisc allnoconfig gcc-16.1.0
powerpc allnoconfig gcc-16.1.0
riscv allnoconfig gcc-16.1.0
s390 allnoconfig clang-24
sh allnoconfig gcc-16.1.0
sparc allnoconfig gcc-16.1.0
um allnoconfig clang-17
x86_64 allnoconfig clang-22
xtensa allnoconfig gcc-16.1.0
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-05 5:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202609051355.F1T2qXnd-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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
all inboxes | Powered by JetHome®