From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot autobuilder: old builds were nuked?
Date: Fri, 20 Oct 2017 23:21:51 +0200 [thread overview]
Message-ID: <20171020212151.GA2549@scaer> (raw)
In-Reply-To: <4881796E12491D4BB15146FE0209CE6467FA2BC3@DE02WEMBXB.internal.synopsys.com>
Alexei, All,
On 2017-10-20 21:14 +0000, Alexey Brodkin spake thusly:
> I noticed that a lot of even not very old builds are absent on autobuilder.
> In fact only 54 most recent builds are displayed now.
>
> Probably I missed something again but is it intentional move or something went wrong?
The latter.
The machine on which a.b.o. runs had a fatal HDD crash right this
afternoon, just mere hours before Thomas ahd to take a plane.
So it seems he managed to at least recover a working a.b.o server for the
time being.
As for the data, either it is lost with the crash, or it will take
longer to recover/restore, but that will have to wait for Thomas to land
first. ;-)
So: no, you did not miss anything, except Thomas weeping on IRC... ;-]
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| 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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-10-20 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 21:14 [Buildroot] Buildroot autobuilder: old builds were nuked? Alexey Brodkin
2017-10-20 21:21 ` Yann E. MORIN [this message]
2017-10-20 21:29 ` Romain Naour
2017-10-20 22:25 ` Arnout Vandecappelle
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=20171020212151.GA2549@scaer \
--to=yann.morin.1998@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.