Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Some build failures to solve for volunteers
Date: Mon, 23 May 2011 16:31:12 +0200	[thread overview]
Message-ID: <87mxid1ob3.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <BANLkTinD8BNxzLKe8bR940aeFNxANr85vg@mail.gmail.com> ("Daniel Nyström"'s message of "Mon, 23 May 2011 14:42:12 +0200")

>>>>> "Daniel" == Daniel Nystr?m <daniel.nystrom@timeterminal.se> writes:

Hi,

 Daniel> There's no problem running Buildroot builds with Buildbot. I do
 Daniel> actually have one running here locally for our local needs. :)

Here as well.

 Daniel> One could set "make randpackageconfig" as one step of the build
 Daniel> process in the Factory, but that makes it hard to find patterns in the
 Daniel> failing builds, hence my suggestion of one toolchain per slave and all
 Daniel> options enabled. Maybe there's other advantages of random configs?

Well, it's a trade off between us wanting reproducable builds and
wanting to test as many configurations as possible.

My current (private) setup involves randpackageconfig and then archiving
the .config and the entire build log, but that easily grows to something
quite unhandy for querying (E.G. in what other builds with a specific
toolchain config and package A+B but not C did it succeed).

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2011-05-23 14:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-22 15:19 [Buildroot] Some build failures to solve for volunteers Thomas Petazzoni
2011-05-23 12:22 ` Daniel Nyström
2011-05-23 12:28   ` Thomas Petazzoni
2011-05-23 12:42     ` Daniel Nyström
2011-05-23 12:47       ` Thomas Petazzoni
2011-05-23 14:31       ` Peter Korsgaard [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=87mxid1ob3.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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