From: Guenter Roeck <linux@roeck-us.net>
To: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Build and runtime failures with next-20151015
Date: Thu, 15 Oct 2015 09:20:46 -0700 [thread overview]
Message-ID: <561FD25E.4070309@roeck-us.net> (raw)
There are too many failures for me to list it all individually, or to track it all down.
Here is a summary.
Build results:
total: 144 pass: 127 fail: 17
Failed builds:
arc:allnoconfig
arm:allmodconfig
arm64:allmodconfig
avr32:allnoconfig
cris:allnoconfig
i386:defconfig
i386:allnoconfig
mips:allmodconfig
mn10300:asb2303_defconfig
mn10300:asb2364_defconfig
parisc:generic-64bit_defconfig
s390:allmodconfig
sparc32:allmodconfig
sparc64:allmodconfig
um:defconfig
x86_64:defconfig
x86_64:allnoconfig
Qemu test results:
total: 93 pass: 53 fail: 40
Failed tests:
arm:vexpress-a9:arm_vexpress_defconfig:vexpress-v2p-ca9
arm:vexpress-a15:arm_vexpress_defconfig:vexpress-v2p-ca15-tc1
arm:kzm:imx_v6_v7_defconfig
rm:beagle:multi_v7_defconfig:omap3-beagle
arm:beaglexm:multi_v7_defconfig:omap3-beagle-xm
arm:overo:multi_v7_defconfig:omap3-overo-tobi
arm:vexpress-a9:multi_v7_defconfig:vexpress-v2p-ca9
arm:vexpress-a15:multi_v7_defconfig:vexpress-v2p-ca15-tc1
arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zc702
arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zc706
arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zed
arm:smdkc210:multi_v7_defconfig:exynos4210-smdkv310
arm:smdkc210:exynos_defconfig:exynos4210-smdkv310
arm:beagle:omap2plus_defconfig:omap3-beagle
arm:beaglexm:omap2plus_defconfig:omap3-beagle-xm
arm:overo:omap2plus_defconfig:omap3-overo-tobi
arm64:smp:defconfig
arm64:nosmp:defconfig
cris:crisv32_defconfig
mips:mips_malta_defconfig
mips:mipsel_malta_defconfig
powerpc:nosmp:ppc64_book3s_defconfig
powerpc:smp4:ppc64_book3s_defconfig
powerpc:pseries_defconfig
x86:SandyBridge:q35:x86_pc_defconfig
x86:Haswell:pc:x86_pc_defconfig
x86:Nehalem:q35:x86_pc_defconfig
x86:phenom:pc:x86_pc_defconfig
x86:core2duo:q35:x86_pc_nosmp_defconfig
x86:Conroe:isapc:x86_pc_nosmp_defconfig
x86:Opteron_G1:pc:x86_pc_nosmp_defconfig
x86:n270:isapc:x86_pc_nosmp_defconfig
x86_64:SandyBridge:q35:x86_64_pc_defconfig
x86_64:Haswell:q35:x86_64_pc_defconfig
x86_64:core2duo:pc:x86_64_pc_defconfig
x86_64:Nehalem:q35:x86_64_pc_defconfig
x86_64:phenom:pc:x86_64_pc_defconfig
x86_64:Opteron_G1:q35:x86_64_pc_defconfig
x86_64:Opteron_G4:pc:x86_64_pc_nosmp_defconfig
x86_64:IvyBridge:q35:x86_64_pc_nosmp_defconfig
Most if not all of the qemu tests are build failures. I think, though, that there
may also be some runtime failures, currently hidden underneath the build failures.
Details are available at http://server.roeck-us.net:8010/builders in case someone
has the time to track this all down.
Guenter
reply other threads:[~2015-10-15 16:21 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=561FD25E.4070309@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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