Skip to contentSkip to conversation

Autobuild.b.o status

Buildroot Thomas Petazzoni 2 participants 3 messages Oct 21, 2017

lore
Share & tools
lore
#0 lore raw

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

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
#1 lore raw
Quoted 8 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Thomas" == Thomas Petazzoni <[email protected]> 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.

Quoted 5 lines

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?

Quoted 11 lines

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!

Signature · 1 line
Bye, Peter Korsgaard
#2 lore raw

Hello,

Quoted 7 lines · Peter Korsgaard
Quoted 5 lines

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

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