A new version of http://autobuild.buildroot.org
Hello all,
I promised it since a looong time, and finally got around to do it. There is a new version of http://autobuild.buildroot.org online. At first sight, the difference may not be very visible, because most of the changes are in the background, but will allow to add more features over time.
In the background, the changes are that:
* Build results are stored in a MySQL database, which allows to do all kind of statistics.
* In addition to build results themselves, the value of all kconfig options, for all builds, are also stored in the database. This will allow to do queries like "give me all the successful build results of the last 30 days that had BR2_PACKAGE_BLEH=y". For now, there is no public interface to make such queries, but the information is available in the database.
* The results are no longer stored in a single flat directory, with one directory per build result, named after the SHA1. Instead they are stored in results/<first 3 characters of the SHA1>/<SHA1>/. This will allow to overcome the 32.000 limit of files per directories. And in fact, the new http://autobuild.buildroot.org has the entire 50232 build results since this service was started!
It is worth mentioning that URLs of the form
http://autobuild.buildroot.org/results/<SHA1>/ are still working, thanks to a smart Apache rewrite rule. It should be completely transparent, and allows all the Git commit log that we have that refer to build failures to continue to work.
The visible changes are:
* All build results since the start of the service are now visible.
* The main page shows 50 results instead of 25 results.
* You can filter to see only successful results, or failed results, by clicking on "OK" or "NOK". You can also access
http://autobuild.buildroot.org/?status=NOK and
http://autobuild.buildroot.org/?status=OK.
* There is a page http://autobuild.buildroot.org/stats.php, with build stats of the last 30 days, since the beginning of the service, and a nice graph showing success/failures/timeouts/total for each day of the last 30 days.
* The format of the daily e-mail will be different. It will show a classification of the failures by "reason" (i.e failing package), ordered by the package causing the highest number of failures first. Then, the list of all failures will be much shorter, and hopefully easier to read and analyze.
* The full build log is no longer available. Storing those entire build logs was consuming a huge amount of disk space. I assume that the last 100 lines of the build log are sufficient to have a rough idea of what's going. Otherwise, the build can easily be reproduced.
I hope nothing got broken. Build results both from Peter's autobuilders and from my autobuilder continue to arrive and be registered, and I think I didn't miss any of them.
Best regards,
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Thomas" == Thomas Petazzoni <[email protected]> writes:
Thomas> Hello all,
Thomas> I promised it since a looong time, and finally got around to do it. Thomas> There is a new version of http://autobuild.buildroot.org online. At Thomas> first sight, the difference may not be very visible, because most of Thomas> the changes are in the background, but will allow to add more features Thomas> over time.
Cool, thanks!
Signature · 1 line
Bye, Peter Korsgaard
Thomas, All,
On 2013-05-13 23:21 +0200, Thomas Petazzoni spake thusly:
Quoted 2 lines
I promised it since a looong time, and finally got around to do it. There is a new version of http://autobuild.buildroot.org online.
Great, good job! Thank you!
Regards,
Yann E. MORIN.
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'
Quoted 4 lines · Thomas Petazzoni
* The full build log is no longer available. Storing those entire build logs was consuming a huge amount of disk space. I assume that the last 100 lines of the build log are sufficient to have a rough idea of what's going. Otherwise, the build can easily be reproduced.
Still, there have been (very few) situations where the error message
itself was not in the last 100 lines. I think 500 lines is safer.
Regards,
Arnout
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
Dear Arnout Vandecappelle,
Quoted 8 lines · Arnout Vandecappelle
Quoted 4 lines · Thomas Petazzoni
* The full build log is no longer available. Storing those entire build logs was consuming a huge amount of disk space. I assume that the last 100 lines of the build log are sufficient to have a rough idea of what's going. Otherwise, the build can easily be reproduced.
Still, there have been (very few) situations where the error message
itself was not in the last 100 lines. I think 500 lines is safer.
Ok, I'll change that.
Thanks for the suggestion,
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com