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: Guix Day: Notes from the CI session
Date: Wed, 10 Feb 2021 22:11:29 +0100	[thread overview]
Message-ID: <87pn174ohq.fsf@gnu.org> (raw)
In-Reply-To: <87blcr3l1v.fsf@gnu.org> (Mathieu Othacehe's message of "Wed, 10 Feb 2021 18:11:08 +0100")

Hi!

Mathieu Othacehe <othacehe@gnu.org> skribis:

>> I think the status quo of 64-bit ARM for us is untenable. The emulated
>> builds cause mass failures that can't be reproduced on real hardware.
>> There is a growing demand for this platform among hobbyists and hackers
>> who we could convert to Guix contributors!
>
> Following discussions that happened on Monday, I limited the number of
> Berlin workers emulating aarch64 builds by half (see
> abfb17bfec0ba41399fb60e91aa0e98087fab469 on maintenance).
>
> I also raised the number of Cuirass remote workers by machines to four
> (see a5df328e5c833ca2d28105280484626bf4c1adb1 on maintenance).
>
> Thanks to Ricardo support I was able to setup a Wireguard tunnel between
> berlin and the overdrive1. It seems to work pretty well and
> https://ci.guix.gnu.org/workers shows that it is building some packages.
>
> I plan to connect the remaining overdrive machines, 2 at Tobias and 1 at
> Andreas places. If this model of connecting build nodes through VPN
> works sustainably, connecting more ARM workstations hosted at individual
> could be a way to proceed.

Yay, thanks Ricardo & people at the MDC, and thank you!

In machines-for-berlin.scm, there’s also a couple of ARMv7 SBCs that,
while slow (no argument here), are helpful.  Do you think these could be
re-connected as well?

Thanks,
Ludo’.


  parent reply	other threads:[~2021-02-10 21:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08 17:07 Guix Day: Notes from the CI session Ludovic Courtès
2021-02-09 21:45 ` Leo Famulari
2021-02-10 17:11   ` Mathieu Othacehe
2021-02-10 17:27     ` Leo Famulari
2021-02-10 21:11     ` Ludovic Courtès [this message]
2021-02-13 23:12     ` Leo Famulari
2021-02-14  8:42       ` Mathieu Othacehe
2021-02-14 18:57         ` Leo Famulari
2021-02-10 21:47   ` Ludovic Courtès
2021-02-11 21:04   ` Andreas Enge
2021-02-11 21:16     ` Leo Famulari
2021-02-09 21:46 ` Leo Famulari
2021-02-10 14:09   ` branch naming conventions [was Re: Guix Day: Notes from the CI session] Efraim Flashner
2021-02-10 16:49     ` Leo Famulari
2021-02-10 21:49       ` Ludovic Courtès
2021-02-11 21:14         ` Leo Famulari
2021-02-12  9:57           ` Efraim Flashner

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=87pn174ohq.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).