From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-05-17
Date: Sat, 18 May 2013 19:36:29 +0200 [thread overview]
Message-ID: <20130518193629.4367854c@skate> (raw)
In-Reply-To: <20130518063006.E936E52C0F6@lolut.humanoidz.org>
Hello,
On Sat, 18 May 2013 08:30:06 +0200 (CEST), Thomas Petazzoni wrote:
> Build statistics for 2013-05-17
> ===============================
>
> success : 70
> failures : 39
> timeouts : 3
> TOTAL : 112
Ok, I found the reason for the timeouts. The fact that they always
happen on qt5base helped me to understand what's going on: my build
script doesn't automatically enable
BR2_PACKAGE_QT5BASE_LICENSE_APPROVED when Qt5 is selected. My build
script does that for Qt4, but not yet for Qt5.
This is now fixed, so hopefully it should make those timeouts disappear.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-05-18 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-18 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-05-17 Thomas Petazzoni
2013-05-18 17:36 ` Thomas Petazzoni [this message]
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=20130518193629.4367854c@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