From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-03-07
Date: Sat, 8 Mar 2014 12:04:54 +0100 [thread overview]
Message-ID: <20140308110454.GA3254@free.fr> (raw)
In-Reply-To: <20140308073007.50AAF1016F2@stock.ovh.net>
Thomas, All,
On 2014-03-08 08:30 +0100, Thomas Petazzoni spake thusly:
> Detail of failures
> ===================
>
> i686 | CXX Source/JavaScrip... | TIM | http://autobuild.buildroot.net/results/93a3e226f624bc389ad647014c070b66ac83de57/
This one had been running for 12663 seconds, which is 3h 31min 3s at the
moment it _started_ building webkit.
So, it looks like some of the random builds can run for more than the
limit of 4h.
Of course, I'm not saying we should bump the limit. But this is a good
example of why saving build-time.log is useful! ;-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-03-08 11:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-08 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-03-07 Thomas Petazzoni
2014-03-08 11:04 ` Yann E. MORIN [this message]
2014-03-08 14:05 ` Thomas Petazzoni
2014-03-10 6:43 ` Arnout Vandecappelle
2014-03-10 12:12 ` Peter Korsgaard
2014-03-10 13:23 ` Arnout Vandecappelle
2014-03-23 21:24 ` 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=20140308110454.GA3254@free.fr \
--to=yann.morin.1998@free.fr \
--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