All of lore.kernel.org
 help / color / mirror / Atom feed
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 a41a2e2e34a907bd8979a53c58f44287630616e8
Date: Wed, 03 Aug 2022 16:17:51 +0800	[thread overview]
Message-ID: <62ea2f2f.UAhAmZtQ7vyNLiPC%lkp@intel.com> (raw)

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/urgent
branch HEAD: a41a2e2e34a907bd8979a53c58f44287630616e8  scripts/faddr2line: Add CONFIG_DEBUG_INFO check

elapsed time: 720m

configs tested: 53
configs skipped: 2

The following configs have been built successfully.
More configs may be tested in the coming days.

gcc tested configs:
um                             i386_defconfig
um                           x86_64_defconfig
x86_64                              defconfig
x86_64                               rhel-8.3
arm                                 defconfig
i386                                defconfig
powerpc                           allnoconfig
x86_64                           allyesconfig
mips                             allyesconfig
ia64                             allmodconfig
powerpc                          allmodconfig
s390                 randconfig-r044-20220801
riscv                randconfig-r042-20220801
arm64                            allyesconfig
arc                  randconfig-r043-20220801
x86_64               randconfig-a011-20220801
i386                             allyesconfig
arm                              allyesconfig
sh                               allmodconfig
x86_64               randconfig-a012-20220801
x86_64               randconfig-a013-20220801
x86_64               randconfig-a014-20220801
x86_64               randconfig-a015-20220801
m68k                             allmodconfig
i386                 randconfig-a012-20220801
alpha                            allyesconfig
i386                 randconfig-a013-20220801
arc                              allyesconfig
x86_64               randconfig-a016-20220801
i386                 randconfig-a014-20220801
x86_64                          rhel-8.3-func
i386                 randconfig-a011-20220801
x86_64                         rhel-8.3-kunit
i386                 randconfig-a016-20220801
i386                 randconfig-a015-20220801
x86_64                           rhel-8.3-kvm
x86_64                    rhel-8.3-kselftests
x86_64                           rhel-8.3-syz
m68k                             allyesconfig

clang tested configs:
x86_64               randconfig-a002-20220801
x86_64               randconfig-a001-20220801
x86_64               randconfig-a003-20220801
x86_64               randconfig-a004-20220801
x86_64               randconfig-a005-20220801
i386                 randconfig-a001-20220801
x86_64               randconfig-a006-20220801
i386                 randconfig-a002-20220801
hexagon              randconfig-r045-20220801
i386                 randconfig-a003-20220801
i386                 randconfig-a005-20220801
hexagon              randconfig-r041-20220801
i386                 randconfig-a004-20220801
i386                 randconfig-a006-20220801

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-08-03  8:18 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=62ea2f2f.UAhAmZtQ7vyNLiPC%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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.