From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] Random build results now available online
Date: Wed, 21 Mar 2012 12:42:34 +0100 [thread overview]
Message-ID: <4F69BEAA.9070608@lucaceresoli.net> (raw)
In-Reply-To: <20120321101327.49d34f93@skate>
Hi Thomas,
Thomas Petazzoni wrote:
> Hello,
>
> During the Prague and Brussels last Buildroot meetings, we discussed
> the idea of putting online the results of the random configurations
> build that Peter and myself were doing.
>
> This week-end, I want ahead and implemented something. The results of
> both Peter builds and my builds are now visible online at:
>
> http://buildroot.humanoidz.org/
Great! Thank you very much.
> Builds are running 24/7 on several machines (one build server of Free
> Electrons, and multiple machines of the gcc farm), and all results are
> visible online. For each result, one can see:
>
> * the result (OK or NOK)
> * the Git commit id identifying which Buildroot version was used. The
> build machines are updating their version before every build
> * which architecture was targeted
> * which package is failing
> * which machine was used for the build
> * the 100 last lines of the build log (faster than having to download
> the entire build log)
> * the entire build log compressed
> * the Buildroot configuration
Why not saving the defconfig as well?
It would be easier to browse and understand (although the full
config is probably better to reproduce the problem on a different
commit.
Luca
next prev parent reply other threads:[~2012-03-21 11:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 9:13 [Buildroot] Random build results now available online Thomas Petazzoni
2012-03-21 9:27 ` Peter Korsgaard
2012-03-21 9:42 ` Thomas Petazzoni
2012-03-21 9:50 ` Peter Korsgaard
2012-03-21 11:42 ` Luca Ceresoli [this message]
2012-03-21 12:20 ` Thomas Petazzoni
2012-03-21 12:54 ` Peter Korsgaard
2012-03-21 13:00 ` Thomas Petazzoni
2012-03-21 11:48 ` Nikolay Nikolaev
2012-03-21 12:15 ` Thomas Petazzoni
2012-03-21 13:00 ` Thomas Petazzoni
2012-03-21 13:10 ` Nikolay Nikolaev
2012-03-21 13:17 ` 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=4F69BEAA.9070608@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--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