unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org, Benjamin Slade <beoram@gmail.com>
Subject: Re: Guix on aarch64
Date: Thu, 30 Aug 2018 11:49:25 +0200	[thread overview]
Message-ID: <87wos8yyje.fsf@gnu.org> (raw)
In-Reply-To: <87efelw1fr.fsf@netris.org> (Mark H. Weaver's message of "Sun, 26 Aug 2018 12:13:44 -0400")

Hi Mark,

Mark H Weaver <mhw@netris.org> skribis:

> The 'guix publish' TTL is a secondary issue, because, as you say, the
> NARs are only deleted if the corresponding store item has been GC'd.
> The more important question is: what is the policy for deleting GC roots
> on Berlin?

As I wrote, there’s no policy other than “make sure there’s at least N
GiB free.”

I think the ‘guix publish’ TTL is not a secondary issue if the question
is “what does it take for substitutes to remain available?”  GC roots
allow us to retain substitutes regardless of their popularity (so it’s
definitely useful for releases), while the TTL allow us to retain
popular substitutes.

I think I already wrote that I acknowledge the issues you raised and
that we should fix Cuirass to create GC roots for evaluations when we
ask it to.

Ricardo Wurmus <rekado@elephly.net> skribis:

> I think our use of Hydra is not sustainable.  It requires regular manual
> intervention by Mark, careful tuning of SQL queries, conscientious
> clean up of old substitutes, and we have not a single person familiar
> with the Perl code.
>
> We do have people working on Cuirass, though.  Let’s add important
> missing features to Cuirass instead of making efforts to keep Hydra on
> life support.

+1

To be clear, I want us to switch to berlin as the main official
substitute server in the coming weeks.  Emacs-build-farm and the web
interface are becoming pretty nice.  There _are_ missing features and
rough edges, but I’d like us to focus on addressing those.

The Cuirass web interface code is nice and pleasant to work with, so I
encourage everyone to take a look and add whatever they deem important!

  https://git.savannah.gnu.org/cgit/guix/guix-cuirass.git/tree/src/cuirass/http.scm
  https://git.savannah.gnu.org/cgit/guix/guix-cuirass.git/tree/src/cuirass/templates.scm

I also think it’s important to be able to react calmly and
constructively to issues like the one Benjamin reported.  It’s not a
minor issue, but if we want to be address it in good conditions, we have
to keep cool and focus on concrete incremental steps we can take to
address it, while also keeping in mind our longer-term goals.

Thanks,
Ludo’.

      parent reply	other threads:[~2018-08-30  9:50 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
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 [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=87wos8yyje.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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).