From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Autobuild.b.o status
Date: Sat, 21 Oct 2017 08:04:44 +0200 [thread overview]
Message-ID: <20171021080444.648fcfa1@windsurf> (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
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next reply other threads:[~2017-10-21 6:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-21 6:04 Thomas Petazzoni [this message]
2017-10-21 6:18 ` [Buildroot] Autobuild.b.o status Peter Korsgaard
2017-10-21 7:44 ` 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=20171021080444.648fcfa1@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--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