Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-03-05
Date: Fri, 7 Mar 2014 09:17:18 +0100	[thread overview]
Message-ID: <20140307091718.2155e87b@skate> (raw)
In-Reply-To: <20140306225641.59c3c535@skate>

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 |                        ^[[7m>>> | 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

  reply	other threads:[~2014-03-07  8:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-03-05 Thomas Petazzoni
2014-03-06 17:08 ` Arnout Vandecappelle
2014-03-06 21:56   ` Thomas Petazzoni
2014-03-07  8:17     ` Thomas Petazzoni [this message]
2014-03-07 10:58       ` Thomas Petazzoni

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=20140307091718.2155e87b@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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