From: Christopher Baines <mail@cbaines.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org, guix-sysadmin@gnu.org
Subject: Re: data.guix.gnu.org problem with revision 33d2574
Date: Tue, 21 Sep 2021 21:31:55 +0100 [thread overview]
Message-ID: <87fstxy8c7.fsf@cbaines.net> (raw)
In-Reply-To: <867dfacqth.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
zimoun <zimon.toutoune@gmail.com> writes:
> Hi Chris,
>
> On Fri, 17 Sep 2021 at 18:42, Christopher Baines <mail@cbaines.net> wrote:
>> Christopher Baines <mail@cbaines.net> writes:
>>
>>> In summary: data.guix.gnu.org is going to be down while I attempt to
>>> restore a backup from earlier this week.
>>
>> The restore was actually quicker than I expected, only taking ~2 hours,
>> so data.guix.gnu.org is back now.
>
> Cool! Thank you!
>
>> It's still going to take some time to catch up and process recent
>> revisions. I also forgot about the build data being sent over from
>> bordeaux.guix.gnu.org, so I'll need to work out some way to replay the
>> events since Monday so that data.guix.gnu.org isn't missing that
>> information. Until that point, the build information won't be correct/up
>> to date.
>
> A question. :-) The “Builds” field shows bordeaux.guix.gnu.org and not
> ci.guix.gnu.org, right? Does data.guix.gnu.org still process Berlin?
Correct, the version of Cuirass currently deployed on ci.guix.gnu.org
doesn't support sending data to the Guix Data Service.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2021-09-21 20:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 14:48 data.guix.gnu.org problem with revision 33d2574 Christopher Baines
2021-09-17 17:42 ` Christopher Baines
2021-09-21 7:48 ` zimoun
2021-09-21 20:31 ` Christopher Baines [this message]
2021-09-24 9:36 ` zimoun
2021-09-23 20:22 ` Ludovic Courtès
2021-09-24 9:20 ` Christopher Baines
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fstxy8c7.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=guix-devel@gnu.org \
--cc=guix-sysadmin@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).