[<prev] [next>] [day] [month] [year] [list]
Message-ID: <75d5be41-1892-287d-81ff-55814a7553b1@roeck-us.net>
Date: Sat, 16 Jun 2018 21:43:02 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>
Subject: v4.18-rc1: Build and qemu test results
Build results:
total: 134 pass: 113 fail: 21
Failed builds:
arm:allmodconfig
c6x:dsk6455_defconfig
c6x:evmc6457_defconfig
c6x:evmc6678_defconfig
h8300:allnoconfig
h8300:edosk2674_defconfig
h8300:h8300h-sim_defconfig
h8300:h8s-sim_defconfig
i386:allyesconfig
i386:allmodconfig
ia64:defconfig
ia64:allnoconfig
mips:defconfig
mips:allnoconfig
mips:defconfig
nds32:defconfig
nds32:allnoconfig
s390:allmodconfig
sparc32:allmodconfig
unicore32:defconfig
unicore32:allnoconfig
Qemu test results:
total: 150 pass: 146 fail: 4
Failed tests:
mips:malta_defconfig:nosmp
mips:malta_defconfig:smp
mips64:malta_defconfig:nosmp
mips64:malta_defconfig:smp
Build errors as well as the qemu test failures are mostly due to
some last minute changes around memblock_virt_alloc_try_nid_raw()
and similar functions (also seen in next-20180615, but not in
next-20180614). There are also a few other errors which have
accumulated during the commit window. Interestingly, almost all
build errors started to be seen in -next only _after_ the commit
window opened. Go figure.
Details are available at http://kerneltests.org/builders/.
Guenter
Powered by blists - more mailing lists