unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Release progress, week 6
Date: Mon, 21 Nov 2022 11:02:38 +0100	[thread overview]
Message-ID: <87ilj8mxq9.fsf@gnu.org> (raw)
In-Reply-To: <87tu2wujk5.fsf@gnu.org> (Mathieu Othacehe's message of "Fri, 18 Nov 2022 20:52:26 +0100")

Hi!

Mathieu Othacehe <othacehe@gnu.org> skribis:

> Hello,
>
>>        It would seem that a lot of aarch64 builds are queued but not
>>        getting processed.  Any idea how to investigate that, Mathieu?
>
> That would be because we only had a single ARM machine available till
> this week (kreuzberg). It seems that overdrive1 and grunewald are back
> though!
>
> I also noticed that my recent remote worker fix was not working as
> expected. The workers are not blocked anymore after a remote server
> disconnection but some builds are flagged as submitted even though they
> are not received by the worker.

OK, that would explain it.

>>      Should we send out a call for testing the installer?  Looks like
>>      we’re ready, no?
>
> Sure, I'll take care of that on Monday.

I’m thinking we might as well do a proper RC1, produced by “make
release”.  Maybe not today, but tomorrow we may have everything ready?

Thanks,
Ludo’.


      reply	other threads:[~2022-11-21 10:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17 16:04 Release progress, week 6 Ludovic Courtès
2022-11-17 20:12 ` Efraim Flashner
2022-11-21 10:04   ` Ludovic Courtès
2022-11-18 19:52 ` Mathieu Othacehe
2022-11-21 10:02   ` Ludovic Courtès [this message]

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=87ilj8mxq9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=othacehe@gnu.org \
    /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).