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 2012-06-13
Date: Fri, 15 Jun 2012 10:19:17 +0200	[thread overview]
Message-ID: <20120615101917.2c757be3@skate> (raw)
In-Reply-To: <CAPNngRMBN95AdPLA8LrOwUhSVEM1p_VRtTUyf_wbO9T5JHfeFw@mail.gmail.com>

Hello,

Le Fri, 15 Jun 2012 01:16:03 -0300,
Milton Soares Filho <milton.soares.filho@gmail.com> a ?crit :

> Could we dispose of more info (extra field) so it's easier to
> filter-out failed builds using custom external toolchains? Found them
> too noisy when randomly bug-hunting.

Yes, I'm thinking of adding a 'toolchain-description.txt' file to every
build, that would describe the toolchain that has been used (Buildroot
config used to build the toolchain, CT-NG config used to build the
toolchain, etc.).

Would this be good for you?

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-06-15  8:19 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 [this message]
2012-06-15 14:57     ` Milton Soares Filho
2012-06-15 15:02       ` Thomas Petazzoni
     [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=20120615101917.2c757be3@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