From: Guenter Roeck <linux@roeck-us.net>
To: Mark Brown <broonie@kernel.org>
Cc: linux-next@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
linux-kernel@vger.kernel.org, Olof Johansson <olof@lixom.net>
Subject: Re: linux-next: Tree for Oct 3
Date: Fri, 4 Oct 2013 12:45:04 -0700 [thread overview]
Message-ID: <20131004194504.GA32457@roeck-us.net> (raw)
In-Reply-To: <20131004102839.GJ27287@sirena.org.uk>
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
next prev parent reply other threads:[~2013-10-04 19:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 1:02 linux-next: Tree for Oct 3 Mark Brown
2013-10-04 5:23 ` Guenter Roeck
2013-10-04 5:41 ` Olof Johansson
2013-10-04 13:44 ` Guenter Roeck
2013-10-04 14:34 ` Mark Brown
2013-10-04 17:00 ` Olof Johansson
2013-10-04 17:52 ` Guenter Roeck
2013-10-04 17:04 ` Olof Johansson
2013-10-05 2:07 ` Guenter Roeck
2013-10-04 10:28 ` Mark Brown
2013-10-04 19:45 ` Guenter Roeck [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-03 3:33 Stephen Rothwell
2019-10-03 4:34 Stephen Rothwell
2018-10-03 11:39 Stephen Rothwell
2016-10-03 4:19 Stephen Rothwell
2014-10-03 7:56 Stephen Rothwell
2012-10-03 7:30 Stephen Rothwell
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=20131004194504.GA32457@roeck-us.net \
--to=linux@roeck-us.net \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--cc=thierry.reding@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).