[Buildroot] Autobuild.b.o status

[Buildroot] Autobuild.b.o status

[Thomas Petazzoni]

Hello,

As several of you realized, autobuild.b.o had a problem yesterday.
Indeed, the server that hosts this (which is my own private server)
suffered a hard disk failure. The hard disk was replaced within an hour
after the incident, but of course it means the setup and data was lost.

Due to the size of the data involved in the autobuilders (gigabytes of
logs), I never bothered doing backups, so effectively the history of
build results is lost. Retrospectively, now that I realize that it
means all build result URLs that we embed in the commit logs are
broken, I think making a back up of those results does make sense.

Anyway, the previous results are lost. The current status is that the
MySQL database is up and running, as well as the web site (for both
viewing the results and submitting results). This was the minimal setup
I wanted to restore in order to start collecting results.

The main thing that remains to do is the e-mail notifications, which
currently won't happen. I will restore this as soon as possible.

It is of course an interesting illustration of Murphy's law to have
such a hard disk failure the day before the Buildroot Developers
meeting.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

[Buildroot] Autobuild.b.o status

[Peter Korsgaard]

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

 > Hello,
 > As several of you realized, autobuild.b.o had a problem yesterday.
 > Indeed, the server that hosts this (which is my own private server)
 > suffered a hard disk failure. The hard disk was replaced within an hour
 > after the incident, but of course it means the setup and data was lost.

 > Due to the size of the data involved in the autobuilders (gigabytes of
 > logs), I never bothered doing backups, so effectively the history of
 > build results is lost. Retrospectively, now that I realize that it
 > means all build result URLs that we embed in the commit logs are
 > broken, I think making a back up of those results does make sense.

Out of interest, how many gigabytes are we talking about approx?

 > Anyway, the previous results are lost. The current status is that the
 > MySQL database is up and running, as well as the web site (for both
 > viewing the results and submitting results). This was the minimal setup
 > I wanted to restore in order to start collecting results.

 > The main thing that remains to do is the e-mail notifications, which
 > currently won't happen. I will restore this as soon as possible.

 > It is of course an interesting illustration of Murphy's law to have
 > such a hard disk failure the day before the Buildroot Developers
 > meeting.

Indeed :/ Thanks for getting it up and running again so fast!

-- 
Bye, Peter Korsgaard

[Buildroot] Autobuild.b.o status

[Thomas Petazzoni]

Hello,

On Sat, 21 Oct 2017 08:18:26 +0200, Peter Korsgaard wrote:

>  > Due to the size of the data involved in the autobuilders (gigabytes of
>  > logs), I never bothered doing backups, so effectively the history of
>  > build results is lost. Retrospectively, now that I realize that it
>  > means all build result URLs that we embed in the commit logs are
>  > broken, I think making a back up of those results does make sense.  
> 
> Out of interest, how many gigabytes are we talking about approx?

Now that the data is lost, I obviously don't have numbers anymore, but
it was in the order of a few tens of gigabytes.

Right now, we have 175 results and it's 56 MB of log/configs (i.e not
counting the MySQL database size). I think we had 200.000 build
results, so that would mean ~64 GB of data.

An ASCII dump of the SQL database right now (with 175 results) is 64 MB.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com