Re: linux-next: Tree for Oct 3

From: Guenter Roeck
Date: Fri Oct 04 2013 - 15:45:19 EST


On Fri, Oct 04, 2013 at 11:28:39AM +0100, Mark Brown wrote:
> On Thu, Oct 03, 2013 at 10:23:39PM -0700, Guenter Roeck wrote:
> > On 10/03/2013 06:02 PM, Mark Brown wrote:
>
> > >Due to the length of time taken to run all the allmodconfigs I skipped
> > >the defconfig tests; I know Olof has the ARM stuff covered in his
> > >autobuilder. I'm going to use allyesconfig tomorrow since that should
> > >run faster so hopefully I can cover the ARM, i386 and x86_64 configs
> > >again.
>
> > I could try to set up the buildbot farm I am using for -stable candidates
> > to also test the -next tree. Would that help ?
>
> Yes, that'd be great. Like Olof said ARM is pretty well covered but
> adding more platforms would be very helpful.

Ok, here are the results based on v3.12-rc3-3771-gedc72f7.

Build summary:
total: 110 pass: 86 skipped: 4 fail: 20

'skipped' means the configuration does not (or no longer) exist.

Failed builds:
arm:allmodconfig
arm:ape6evm_defconfig
arm:marzen_defconfig
arm:armadillo800eva_defconfig
arm:mackerel_defconfig
blackfin:defconfig
metag:defconfig
metag:meta1_defconfig
metag:meta2_defconfig
metag:meta2_smp_defconfig
mips:defconfig
mips:bcm63xx_defconfig
mips:nlm_xlp_defconfig
mips:fuloong2e_defconfig
mips:e55_defconfig
mips:malta_defconfig
powerpc:ppc64e_defconfig
powerpc:chroma_defconfig
powerpc:mpc85xx_smp_defconfig
sparc64:allmodconfig

mips and mips64 qemu tests fail as well. mips test builds but hangs early in
boot, mips64 fails to build.

On the plus side, the sh qemu warning (WARNING traceback during boot)
is no longer observed.

Details are at http://server.roeck-us.net:8010/builders.

If everything works as intended, updates to the repository should trigger an
automatic re-build. No guarantees, though - I had some trouble with the initial
checkout.

Guenter

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/