From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [paulmck-rcu:bulkexptest.2022.06.13a] BUILD SUCCESS 3669299c41d84669c40f0d6bfe29f1e15b1a6858
Date: Wed, 15 Jun 2022 11:19:08 +0800 [thread overview]
Message-ID: <62a94fac.dLNSm4z0D7kp81Po%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git bulkexptest.2022.06.13a
branch HEAD: 3669299c41d84669c40f0d6bfe29f1e15b1a6858 rcutorture: Add bulk test of expedited primitives
elapsed time: 1768m
configs tested: 105
configs skipped: 3
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
arm64 defconfig
arm64 allyesconfig
arm allmodconfig
arm defconfig
arm allyesconfig
i386 randconfig-c001-20220613
m68k m5249evb_defconfig
mips bigsur_defconfig
m68k m5275evb_defconfig
xtensa virt_defconfig
arm mini2440_defconfig
powerpc pq2fads_defconfig
powerpc motionpro_defconfig
csky alldefconfig
arm axm55xx_defconfig
sh microdev_defconfig
arm jornada720_defconfig
arm u8500_defconfig
microblaze defconfig
arc axs103_smp_defconfig
ia64 defconfig
ia64 allmodconfig
ia64 allyesconfig
x86_64 randconfig-k001-20220613
m68k defconfig
m68k allmodconfig
m68k allyesconfig
nios2 defconfig
arc allyesconfig
csky defconfig
nios2 allyesconfig
alpha defconfig
alpha allyesconfig
h8300 allyesconfig
xtensa allyesconfig
arc defconfig
sh allmodconfig
s390 defconfig
s390 allmodconfig
parisc defconfig
parisc64 defconfig
parisc allyesconfig
s390 allyesconfig
sparc allyesconfig
i386 debian-10.3-kselftests
i386 debian-10.3
i386 defconfig
sparc defconfig
i386 allyesconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allnoconfig
powerpc allmodconfig
x86_64 randconfig-a015-20220613
x86_64 randconfig-a014-20220613
x86_64 randconfig-a011-20220613
x86_64 randconfig-a016-20220613
x86_64 randconfig-a012-20220613
x86_64 randconfig-a013-20220613
i386 randconfig-a013-20220613
i386 randconfig-a011-20220613
i386 randconfig-a014-20220613
i386 randconfig-a012-20220613
i386 randconfig-a015-20220613
i386 randconfig-a016-20220613
riscv randconfig-r042-20220613
arc randconfig-r043-20220613
s390 randconfig-r044-20220613
riscv defconfig
riscv nommu_virt_defconfig
riscv rv32_defconfig
riscv nommu_k210_defconfig
riscv allnoconfig
riscv allmodconfig
riscv allyesconfig
x86_64 rhel-8.3-kselftests
um i386_defconfig
um x86_64_defconfig
x86_64 kexec
x86_64 defconfig
x86_64 allyesconfig
x86_64 rhel-8.3
x86_64 rhel-8.3-func
x86_64 rhel-8.3-syz
x86_64 rhel-8.3-kunit
clang tested configs:
mips malta_kvm_defconfig
arm collie_defconfig
mips sb1250_swarm_defconfig
powerpc katmai_defconfig
powerpc ge_imp3a_defconfig
x86_64 randconfig-a003-20220613
x86_64 randconfig-a006-20220613
x86_64 randconfig-a001-20220613
x86_64 randconfig-a005-20220613
x86_64 randconfig-a002-20220613
x86_64 randconfig-a004-20220613
i386 randconfig-a002-20220613
i386 randconfig-a003-20220613
i386 randconfig-a001-20220613
i386 randconfig-a005-20220613
i386 randconfig-a004-20220613
i386 randconfig-a006-20220613
hexagon randconfig-r041-20220613
hexagon randconfig-r045-20220613
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-06-15 3:20 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=62a94fac.dLNSm4z0D7kp81Po%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®