From: kbuild test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:pending-fixes] BUILD INCOMPLETE e24e77e0398319862489009664e26837dd31e851
Date: Sun, 19 Jan 2020 11:36:54 +0800 [thread overview]
Message-ID: <5e23ced6.hWt2aVjWC9HHHWL/%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
branch HEAD: e24e77e0398319862489009664e26837dd31e851 Merge remote-tracking branch 'drm-misc-fixes/for-linux-next-fixes'
TIMEOUT after 2896m
Sorry we cannot finish the testset for your branch within a reasonable time.
It's our fault -- either some build server is down or some build worker is busy
doing bisects for _other_ trees. The branch will get more complete coverage and
possible error reports when our build infrastructure is restored or catches up.
There will be no more build success notification for this branch head, but you
can expect reasonably good test coverage after waiting for 1 day.
configs timed out: 45
alpha defconfig
arm allmodconfig
arm allnoconfig
arm allyesconfig
arm at91_dt_defconfig
arm efm32_defconfig
arm exynos_defconfig
arm multi_v5_defconfig
arm multi_v7_defconfig
arm shmobile_defconfig
arm sunxi_defconfig
arm64 allmodconfig
arm64 allnoconfig
arm64 allyesconfig
arm64 defconfig
csky defconfig
i386 alldefconfig
i386 allnoconfig
i386 allyesconfig
i386 defconfig
ia64 alldefconfig
ia64 allmodconfig
ia64 allnoconfig
ia64 allyesconfig
ia64 defconfig
mips 32r2_defconfig
mips 64r6el_defconfig
mips allmodconfig
mips allnoconfig
mips allyesconfig
mips fuloong2e_defconfig
mips malta_kvm_defconfig
nds32 allnoconfig
nds32 defconfig
s390 alldefconfig
s390 allmodconfig
s390 allnoconfig
s390 allyesconfig
s390 debug_defconfig
s390 defconfig
s390 zfcpdump_defconfig
sparc64 allmodconfig
sparc64 allnoconfig
sparc64 allyesconfig
sparc64 defconfig
configs tested: 60
configs skipped: 1
m68k multi_defconfig
m68k m5475evb_defconfig
h8300 h8300h-sim_defconfig
h8300 edosk2674_defconfig
m68k sun3_defconfig
h8300 h8s-sim_defconfig
m68k allmodconfig
riscv rv32_defconfig
riscv allnoconfig
riscv defconfig
riscv allmodconfig
riscv nommu_virt_defconfig
riscv allyesconfig
sh allmodconfig
sh rsk7269_defconfig
sh sh7785lcr_32bit_defconfig
sh allnoconfig
sh titan_defconfig
riscv randconfig-a001-20200117
parisc randconfig-a001-20200117
m68k randconfig-a001-20200117
alpha randconfig-a001-20200117
nds32 randconfig-a001-20200117
xtensa common_defconfig
openrisc or1ksim_defconfig
nios2 3c120_defconfig
xtensa iss_defconfig
c6x evmc6678_defconfig
c6x allyesconfig
nios2 10m50_defconfig
openrisc simple_smp_defconfig
parisc c3000_defconfig
parisc b180_defconfig
parisc defconfig
parisc allnoconfig
um x86_64_defconfig
um i386_defconfig
um defconfig
arc allyesconfig
powerpc defconfig
microblaze nommu_defconfig
powerpc ppc64_defconfig
powerpc rhel-kconfig
microblaze mmu_defconfig
arc defconfig
powerpc allnoconfig
x86_64 randconfig-b003-20200118
i386 randconfig-b003-20200118
i386 randconfig-b002-20200118
i386 randconfig-b001-20200118
sparc64 randconfig-a001-20200118
microblaze randconfig-a001-20200118
nios2 randconfig-a001-20200118
h8300 randconfig-a001-20200118
c6x randconfig-a001-20200118
x86_64 lkp
x86_64 rhel
x86_64 rhel-7.6
x86_64 fedora-25
x86_64 kexec
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
reply other threads:[~2020-01-19 3:37 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=5e23ced6.hWt2aVjWC9HHHWL/%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.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