From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Fri, 7 Mar 2014 09:17:18 +0100 Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-03-05 In-Reply-To: <20140306225641.59c3c535@skate> References: <20140306073010.F1C12100E3F@stock.ovh.net> <5318AB8C.9050802@mind.be> <20140306225641.59c3c535@skate> Message-ID: <20140307091718.2155e87b@skate> List-Id: To: buildroot@busybox.net Hello, On Thu, 6 Mar 2014 22:56:41 +0100, Thomas Petazzoni wrote: > Dear Arnout Vandecappelle, > > On Thu, 06 Mar 2014 18:08:28 +0100, Arnout Vandecappelle wrote: > > On 06/03/14 08:30, Thomas Petazzoni wrote: > > > i686 | >>> | TIM | http://autobuild.buildroot.net/results/9d49f31c9dc16d2a2a4aafa535fbb5ea7e24a66f/ > > > > To be able to do _something_ useful in a case like this, it would be > > nice if output/build/build-time.log was also saved. > > I've tentatively modified the scripts on my build server to include > build-time.log in the build results. We'll see if it works. It works: http://autobuild.buildroot.org/results/834/8348f41edf138433d1d8a1eeb1d426e2797ba4c5//build-time.log http://autobuild.buildroot.org/results/946/946e34a19f3189f8348d8f1f160d5d0c3d19194c//build-time.log We'll see the next time one of these timeouts show up again. Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com