[Buildroot] Random build results now available online

[Buildroot] Random build results now available online

[Thomas Petazzoni]

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/

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

In the following days, I will:

 * Put online the source code of the web interface. It consists of a
   bit of crappy PHP code, but I'll put it online in a Git repository
   so that everyone can contribute to its improvement.

 * Put online a documentation that details how other people can
   contribute build results (it's basically a matter of creating a
   tarball with some particular files, and uploading this tarball over
   http)

The website along with all build results are currently hosted on a
personal server. If there a wish to migrate this on a more common
server, I'll be happy to do so, provided that this server has the
necessary ressources (dependencies and disk space).

Best regards,

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

[Buildroot] Random build results now available online

[Peter Korsgaard]

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 Thomas> Hello,
 Thomas> During the Prague and Brussels last Buildroot meetings, we discussed
 Thomas> the idea of putting online the results of the random configurations
 Thomas> build that Peter and myself were doing.

 Thomas> This week-end, I want ahead and implemented something. The results of
 Thomas> both Peter builds and my builds are now visible online at:

 Thomas>  http://buildroot.humanoidz.org/

Once again, thanks!

How about adding a .buildroot.{net,org} DNS entry for it, though? How
about autobuild.buildroot.{net,org} or something like that?

 Thomas> The website along with all build results are currently hosted on a
 Thomas> personal server. If there a wish to migrate this on a more common
 Thomas> server, I'll be happy to do so, provided that this server has the
 Thomas> necessary ressources (dependencies and disk space).

We can perhaps talk with the osuosl.org guys about that.

-- 
Bye, Peter Korsgaard

[Buildroot] Random build results now available online

[Thomas Petazzoni]

Le Wed, 21 Mar 2012 10:27:49 +0100,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :

>  Thomas> This week-end, I want ahead and implemented something. The results of
>  Thomas> both Peter builds and my builds are now visible online at:
> 
>  Thomas>  http://buildroot.humanoidz.org/
> 
> Once again, thanks!
> 
> How about adding a .buildroot.{net,org} DNS entry for it, though? How
> about autobuild.buildroot.{net,org} or something like that?

As discussed on IRC, done on my side (Apache configuration). Provided
the DNS entries are added and pointed to 213.246.36.146, it should work.

>  Thomas> The website along with all build results are currently hosted on a
>  Thomas> personal server. If there a wish to migrate this on a more common
>  Thomas> server, I'll be happy to do so, provided that this server has the
>  Thomas> necessary ressources (dependencies and disk space).
> 
> We can perhaps talk with the osuosl.org guys about that.

Right. I have no problem to continue hosting this, it's just that I
think things are better if they are centralized on a server that
at least a few Buildroot developers have access to.

Best regards,

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

[Buildroot] Random build results now available online

[Peter Korsgaard]

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

Hi,

 >> How about adding a .buildroot.{net,org} DNS entry for it, though? How
 >> about autobuild.buildroot.{net,org} or something like that?

 Thomas> As discussed on IRC, done on my side (Apache configuration). Provided
 Thomas> the DNS entries are added and pointed to 213.246.36.146, it should work.

The DNS (cname) records are added now.

http://autobuild.buildroot.net
http://autobuild.buildroot.org

 >> We can perhaps talk with the osuosl.org guys about that.

 Thomas> Right. I have no problem to continue hosting this, it's just that I
 Thomas> think things are better if they are centralized on a server that
 Thomas> at least a few Buildroot developers have access to.

True. Having the code in git is already a good start though.

-- 
Bye, Peter Korsgaard

[Buildroot] Random build results now available online

[Luca Ceresoli]

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

[Buildroot] Random build results now available online

[Thomas Petazzoni]

Le Wed, 21 Mar 2012 12:42:34 +0100,
Luca Ceresoli <luca@lucaceresoli.net> a ?crit :

> 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.

I hesitated about this, but ok, I can add the defconfig file as well.

Peter, can you include a file named 'defconfig' in the tarball you
upload?

Thanks,

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

[Buildroot] Random build results now available online

[Peter Korsgaard]

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 Thomas> Le Wed, 21 Mar 2012 12:42:34 +0100,
 Thomas> Luca Ceresoli <luca@lucaceresoli.net> a ?crit :

 >> 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.

 Thomas> I hesitated about this, but ok, I can add the defconfig file as well.

 Thomas> Peter, can you include a file named 'defconfig' in the tarball you
 Thomas> upload?

Ok, I've changed the script to run make savedefconfig and store that as
well.

-- 
Bye, Peter Korsgaard

[Buildroot] Random build results now available online

[Thomas Petazzoni]

Le Wed, 21 Mar 2012 13:54:59 +0100,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :

> Ok, I've changed the script to run make savedefconfig and store that as
> well.

Good. The website now shows a link to the defconfig if the tarball
contained it. At the moment of writing this e-mail, the last build I
have submitted contained such a defconfig, and the link has been
properly created by the web frontend.

Regards,

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

[Buildroot] Random build results now available online

[Nikolay Nikolaev]

Hello,

will it be hard to add an RSS feed to the site? I guess other may find
it useful too.
Thanks.

regards,
Nikolay Nikolaev

[Buildroot] Random build results now available online

[Thomas Petazzoni]

Hello,

Le Wed, 21 Mar 2012 13:48:49 +0200,
Nikolay Nikolaev <nicknickolaev@gmail.com> a ?crit :

> will it be hard to add an RSS feed to the site? I guess other may find
> it useful too.

Good idea, I'll try to do that.

Best regards,

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

[Buildroot] Random build results now available online

[Thomas Petazzoni]

Le Wed, 21 Mar 2012 13:48:49 +0200,
Nikolay Nikolaev <nicknickolaev@gmail.com> a ?crit :

> will it be hard to add an RSS feed to the site? I guess other may find
> it useful too.

It is a bit basic at the moment (suggestions welcome), but it seems to
work:

  http://buildroot.humanoidz.org/rss.php

Best regards,

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

[Buildroot] Random build results now available online

[Nikolay Nikolaev]

On Wed, Mar 21, 2012 at 3:00 PM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Le Wed, 21 Mar 2012 13:48:49 +0200,
> Nikolay Nikolaev <nicknickolaev@gmail.com> a ?crit :
>
>> will it be hard to add an RSS feed to the site? I guess other may find
>> it useful too.
>
> It is a bit basic at the moment (suggestions welcome), but it seems to
> work:
>
> ?http://buildroot.humanoidz.org/rss.php

Suggestion: Can you add "Arch" and "Failed reason" to the failed
items? That way it's clearly visible that
"liburcu-0.6.7" failed building for "arm".

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

[Buildroot] Random build results now available online

[Thomas Petazzoni]

Le Wed, 21 Mar 2012 15:10:25 +0200,
Nikolay Nikolaev <nicknickolaev@gmail.com> a ?crit :

> Suggestion: Can you add "Arch" and "Failed reason" to the failed
> items? That way it's clearly visible that
> "liburcu-0.6.7" failed building for "arm".

It is already the case. Taking one particular build example, the title
is:

"""
Build failed at 2012-03-21 13:49:06
"""

and the description is

"""
A Buildroot build result, submitted by Peter Korsgaard (gcc10)
 failed. The reason of the failure is: liblockfile-1.08. The build used
the Git commit id 832b1ef746e7df252ff42b19f6083f3716f70eb9 and was
targetting the arm architecture.
"""

However, the description is only available in the
<description>...</description> field. Maybe some RSS readers only look
at the <content:encoded>...</content:encoded> field, which contains an
HTML version of the description. I will add it later and we'll see if
it fixes things for your RSS reader.

Best regards,

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