From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2012-06-13
Date: Fri, 15 Jun 2012 17:02:03 +0200 [thread overview]
Message-ID: <20120615170203.6bc1e19a@skate> (raw)
In-Reply-To: <CAPNngRN=e2BaOgMutb-xiDuy-mxs-sO_6YpJ1sb8ezGr+ZXjLA@mail.gmail.com>
Le Fri, 15 Jun 2012 11:57:42 -0300,
Milton Soares Filho <milton.soares.filho@gmail.com> a ?crit :
> Perhaps including another field at the summary just to tell the type
> of the toolchain would be enough. The use-case is filter-out
> configurations where other users can not easily reproduce the
> conditions whether the build has failed, such as custom external
> toolchains provided by third-parties or paid-for development kits.
None of the toolchains that are currently being used for the autobuild
tests are private toolchains. They are either:
* Publicly available CodeSourcery toolchains
* Publicly available Linaro toolchains
* Toolchains built with Crosstool-NG
* Toolchains built with Buildroot
I think we should rather document how to get or build those toolchains,
or even make them available (easy for CodeSourcery, Linaro and
Crosstool-NG, more complicated for Buildroot toolchains since those
toolchains are not relocatable as of today).
Since about 90% of the builds are done with external toolchains, simply
filtering out all test cases done with external toolchains will just
leave you with only a few test builds.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-06-15 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 6:31 [Buildroot] [autobuild.buildroot.net] Build results for 2012-06-13 Thomas Petazzoni
2012-06-15 4:16 ` Milton Soares Filho
2012-06-15 8:19 ` Thomas Petazzoni
2012-06-15 14:57 ` Milton Soares Filho
2012-06-15 15:02 ` Thomas Petazzoni [this message]
[not found] ` <CAPNngRPqsXQScLZm3xTwaL9umNKxytpVDUh2TmP_Zy7uBeS6Mg@mail.gmail.com>
2012-06-15 15:28 ` 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=20120615170203.6bc1e19a@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