From: "Ludovic Courtès" <ludo@gnu.org>
To: 55848@debbugs.gnu.org
Cc: Ricardo Wurmus <rekado@elephly.net>,
Mathieu Othacehe <othacehe@gnu.org>,
guix-sysadmin <guix-sysadmin@gnu.org>,
Greg Hogan <code@greghogan.com>,
Tom Fitzhenry <tom@tom-fitzhenry.me.uk>
Subject: bug#55848: AArch64 Honeycomb builders are inactive
Date: Mon, 29 Aug 2022 15:30:07 +0200 [thread overview]
Message-ID: <874jxv6uu8.fsf_-_@gnu.org> (raw)
In-Reply-To: <87wnbgyzwl.fsf_-_@gnu.org> ("Ludovic Courtès"'s message of "Wed, 10 Aug 2022 15:46:34 +0200")
Hello!
Ludovic Courtès <ludo@gnu.org> skribis:
> I’m currently reconfiguring pankow and grunewald⁰ from berlin with ‘guix
> deploy’ to include the fix above¹, but it’s gonna take a while as it’s
> currently building GCC…
That eventually succeeded and pankow is now reconfigured with the right
daemon settings. \o/
In the meantime, grunewald went off-line so I can’t tell if it’s
properly reconfigured, and kreuzberg is still running the old config I
believe (I cannot log in).
Ricardo, do you have access to these two?
Cheers,
Ludo’.
next prev parent reply other threads:[~2022-08-29 13:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 15:31 bug#55848: [cuirass] workers stalled Mathieu Othacehe
2022-06-08 19:07 ` Greg Hogan
2022-06-11 10:44 ` Tom Fitzhenry
2022-06-12 13:33 ` Ludovic Courtès
2022-06-12 16:10 ` Ricardo Wurmus
2022-06-12 20:22 ` Ludovic Courtès
2022-08-10 13:46 ` bug#55848: AArch64 honeycomb machines aren’t building stuff Ludovic Courtès
2022-08-10 17:55 ` Ricardo Wurmus
2022-08-11 14:06 ` bug#55848: [cuirass] workers stalled Ludovic Courtès
2022-08-29 13:30 ` Ludovic Courtès [this message]
2022-06-19 2:07 ` Tom Fitzhenry
2022-06-20 2:39 ` Maxim Cournoyer
2022-06-20 2:44 ` Tom Fitzhenry
2022-06-20 13:02 ` Maxime Devos
2022-06-21 5:32 ` Maxim Cournoyer
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=874jxv6uu8.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=55848@debbugs.gnu.org \
--cc=code@greghogan.com \
--cc=guix-sysadmin@gnu.org \
--cc=othacehe@gnu.org \
--cc=rekado@elephly.net \
--cc=tom@tom-fitzhenry.me.uk \
/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).