On Thu, Feb 20, 2014 at 8:13 AM, Stephen Warren swarren@wwwdotorg.org wrote:
On 02/20/2014 02:49 AM, Olof Johansson wrote:
On Wed, Feb 19, 2014 at 8:39 AM, Stephen Warren swarren@wwwdotorg.org wrote:
On 02/19/2014 12:27 AM, Olof's autobuilder wrote:
Here are the build results from automated periodic testing.
The tree being built was arm-soc, found at:
http://git.kernel.org/cgit/linux/kernel/git/arm/arm-soc.git (for-next or to-build branch)
Topmost commit:
fe73503 Merge branch 'next/cleanup' into for-next
Build logs (stderr only) can be found at the following link (experimental):
http://arm-soc.lixom.net/buildlogs/arm-soc/v3.14-rc3-46-gfe73503/
...
Failed defconfigs: bcm2835_defconfig
...
I'm not sure why the errors that show up in buildall.arm.bcm2835_defconfig.log.failed didn't show up in the email.
I have a very simple grep command I run, I search for "warning:" and "error:", and neither word is in the error string there.
Ah. Does it make sense to include all stderr, plus any warning/error matches from stdout?
It gets noisy and harder to whitelist warnings that are always there (such as the stack unwind one). All of stderr is available on the website though.
I poked around the ccache mailing lists, seems like current git has some fixes for these type of conditions so I've upgraded my machine to that. Hopefully it'll help.
-Olof