arndale : passed 0:47.26 beaver : passed 1:46.06 cubie : passed 0:50.86 cubie2 : passed 0:58.54 cubox : passed 0:47.74 panda : passed 0:51.84 sama5 : passed 1:44.96 snowball : passed 1:19.07 multi-beaver : passed 0:28.74 multi-panda : passed 0:50.35 multi-snowball : FAILED 0:45.71
Last entries of failed logs below:
========================================================================
Board multi-snowball failure log: -------------------------------------------------
Environment size: 1698/4092 bytes U8500 $ printenv bootargs printenv bootargs bootargs=console=ttyAMA2,115200 root=/dev/mmcblk0p4 rootwait rw debug earlyprintk U8500 $ tftpboot 0x100000 172.16.1.4:/srv/tftp/next/next-20130916/uImage.multi-snowball tftpboot 0x100000 172.16.1.4:/srv/tftp/next/next-20130916/uImage.multi-snowball smc911x: detected LAN9221 controller smc911x: phy initialized smc911x: MAC 08:00:08:1e:0f:44 Using smc911x-0 device TFTP from server 172.16.1.4; our IP address is 172.16.1.109 Filename '/srv/tftp/next/next-20130916/uImage.multi-snowball'. Load address: 0x100000 Loading: *################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################ done Bytes transferred = 3568860 (3674dc hex) U8500 $ bootm 0x100000 bootm 0x100000 ## Booting kernel from Legacy Image at 00100000 ... Image Name: Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3568796 Bytes = 3.4 MB Load Address: 00008000 Entry Point: 00008000 Loading Kernel Image ... OK OK
Starting kernel ...
~$off
Perhaps the emails could include the git tree link? I had no idea what "queue" was for example, until I went back and found Olof's message.
It'd be nice to synchronize the branch names the various builders use. While I now found an explanation in Olof's message re: what's the difference between "next" and "next/master" or "mainline" and "linus/master" in the email subjects, it would be nice if that explanation weren't needed in the future (e.g. someone new coming along and not having been CC'd on Olof's message). Having git links in the reports would probably be enough to solve this too though.
On Mon, Sep 16, 2013 at 10:16 AM, Stephen Warren swarren@wwwdotorg.org wrote:
Perhaps the emails could include the git tree link? I had no idea what "queue" was for example, until I went back and found Olof's message.
Yeah, sorry, I'll add more descriptions when I revise my scripts in the next week or two.
It'd be nice to synchronize the branch names the various builders use. While I now found an explanation in Olof's message re: what's the difference between "next" and "next/master" or "mainline" and "linus/master" in the email subjects, it would be nice if that explanation weren't needed in the future (e.g. someone new coming along and not having been CC'd on Olof's message). Having git links in the reports would probably be enough to solve this too though.
Yep, that'd come a long way. 'queue' in this case is a tree that isn't available via public git though. since it's an application of Greg's quilt series for the -stable queue. I guess I could push it up somewhere.
-Olof
On 09/16/2013 12:25 PM, Olof Johansson wrote:
On Mon, Sep 16, 2013 at 10:16 AM, Stephen Warren swarren@wwwdotorg.org wrote:
Perhaps the emails could include the git tree link? I had no idea what "queue" was for example, until I went back and found Olof's message.
Yeah, sorry, I'll add more descriptions when I revise my scripts in the next week or two.
It'd be nice to synchronize the branch names the various builders use. While I now found an explanation in Olof's message re: what's the difference between "next" and "next/master" or "mainline" and "linus/master" in the email subjects, it would be nice if that explanation weren't needed in the future (e.g. someone new coming along and not having been CC'd on Olof's message). Having git links in the reports would probably be enough to solve this too though.
Yep, that'd come a long way. 'queue' in this case is a tree that isn't available via public git though. since it's an application of Greg's quilt series for the -stable queue. I guess I could push it up somewhere.
Any kind of brief description, such as a link to the quilt file(?) would be fine. I wasn't expecting it to always be machine-parsable for example.
kernel-build-reports@lists.linaro.org
-
build＠lixom.net -
Olof Johansson -
Stephen Warren