From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:perf/urgent] BUILD SUCCESS 030a976efae83f7b6593afb11a8254d42f9290fe
Date: Fri, 25 Nov 2022 05:26:29 +0800 [thread overview]
Message-ID: <637fe185.MMBaqfQrA30EXIQJ%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git perf/urgent
branch HEAD: 030a976efae83f7b6593afb11a8254d42f9290fe perf: Consider OS filter fail
elapsed time: 729m
configs tested: 57
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
um x86_64_defconfig
um i386_defconfig
sh allmodconfig
s390 defconfig
powerpc allnoconfig
arc defconfig
alpha defconfig
s390 allmodconfig
ia64 allmodconfig
mips allyesconfig
powerpc allmodconfig
x86_64 defconfig
x86_64 allyesconfig
x86_64 rhel-8.3
x86_64 allnoconfig
x86_64 rhel-8.3-func
x86_64 rhel-8.3-kselftests
s390 allyesconfig
arc randconfig-r043-20221124
powerpc maple_defconfig
i386 allyesconfig
i386 defconfig
x86_64 rhel-8.3-kvm
x86_64 rhel-8.3-syz
x86_64 rhel-8.3-kunit
i386 randconfig-a012
i386 randconfig-a014
i386 randconfig-a016
sh se7206_defconfig
sh dreamcast_defconfig
arm shmobile_defconfig
powerpc tqm8548_defconfig
powerpc klondike_defconfig
arm64 allyesconfig
arm defconfig
arm allyesconfig
powerpc ep88xc_defconfig
ia64 generic_defconfig
arm multi_v4t_defconfig
x86_64 randconfig-a006
x86_64 randconfig-a004
x86_64 randconfig-a002
m68k allyesconfig
m68k allmodconfig
arc allyesconfig
alpha allyesconfig
i386 randconfig-c001
clang tested configs:
s390 randconfig-r044-20221124
hexagon randconfig-r041-20221124
riscv randconfig-r042-20221124
hexagon randconfig-r045-20221124
x86_64 randconfig-a012
x86_64 randconfig-a014
x86_64 randconfig-a016
i386 randconfig-a002
i386 randconfig-a006
i386 randconfig-a004
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-11-24 21:26 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=637fe185.MMBaqfQrA30EXIQJ%lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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