unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org, Benjamin Slade <beoram@gmail.com>
Subject: Re: Guix on aarch64
Date: Tue, 28 Aug 2018 09:57:49 +0200	[thread overview]
Message-ID: <87r2iic48y.fsf@elephly.net> (raw)
In-Reply-To: <87o9dnsep0.fsf@netris.org>


Hi Mark,

> Ricardo Wurmus <rekado@elephly.net> writes:
>> I think you are overreacting and I really don’t think the sarcastic
>> response is justified.  This kind of communication is very demotivating
>> to me.
>
> Believe it or not, I wasn't conscious of the fact that I was being
> sarcastic or hostile.  Sorry about that.  I'm grasping at straws trying
> to understand your reasoning.

When in doubt my reasoning is probably just lacking information.  I’m
spreading myself a little too thin in trying to read everything on the
mailing lists, writing responses, and trying to fix problems or recruit
people to help in fixing them.  My apologies for the confusion.

I commented specifically on Leo’s statement about build debugging on
Cuirass:

    “I don't actually do any build debugging with Berlin yet because I
     don't know how to use the interface effectively.”

This did not sound like a severe problem with Cuirass to me, but rather
a problem that could be fixed by adding minor features to Cuirass like
the display of build logs.  Leo, could you please tell us what missing
feature in the Cuirass web interface is the most urgent for you to use
the interface effectively?

Another problem that was mentioned is the garbage collection policy on
berlin.guixsd.org, which regularly removes too many built store items.
To address this I could move the store to a 37TB storage device, but I
have been having problems with the lack of multipath support at boot
time.  Obviously, I want berlin.guixsd.org to be reliable, so I’d prefer
to only attach the storage once it is available via multipath, and not
just attach it over a single HBA link.  This is a little tricky as
multipath support needs to be available early during boot.  If
/gnu/store is on a multipath device, then all packages required for
multipath support need to be available in the initrd as statically
linked executables.  I haven’t been able to make this work yet.

> I lack access to both Berlin and to the Aarch64 build slaves, so I can't
> do this.

Oh.  I can remove one of the build machines from Berlin.  But we need
input from Ludovic or Efraim (who currently both host one of the
machines) before we can verify the relocation of one of the machines.

@Ludo: could we remove the aarch64 machine at your place from
berlin.guixsd.org today and add it to Hydra?  I’m available during most
of the day to help test things.

--
Ricardo

  parent reply	other threads:[~2018-08-28  7:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87mutm72n7.fsf@jnanam.net>
     [not found] ` <878t565k85.fsf@lassieur.org>
     [not found]   ` <87k1oq6wgf.fsf@jnanam.net>
2018-08-23  4:58     ` Guix on aarch64 Mark H Weaver
2018-08-23 16:09       ` Benjamin Slade
2018-08-24 10:32       ` Ludovic Courtès
2018-08-24 19:18         ` Ricardo Wurmus
2018-08-26 16:13         ` Mark H Weaver
2018-08-26 18:59           ` Leo Famulari
2018-08-27  8:04             ` Ricardo Wurmus
2018-08-27 18:54               ` Mark H Weaver
2018-08-27 19:11               ` Mark H Weaver
2018-08-27 19:26                 ` Ricardo Wurmus
2018-08-27 21:05                   ` Mark H Weaver
2018-08-27 21:56                     ` Mark H Weaver
2018-08-28  5:39                     ` Mark H Weaver
2018-08-28  7:57                     ` Ricardo Wurmus [this message]
2018-08-28 10:00                       ` Andreas Enge
2018-08-28 15:40                         ` Mark H Weaver
2018-08-28 19:09                       ` Leo Famulari
2018-08-28 19:22                         ` Mark H Weaver
2018-08-27 19:50               ` Leo Famulari
2018-08-27 20:37                 ` Ricardo Wurmus
2018-08-29 20:52               ` Joshua Branson
2018-08-30 20:47                 ` Ricardo Wurmus
2018-08-30  9:49           ` Ludovic Courtès

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=87r2iic48y.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=beoram@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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).