all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Status of armhf-linux and powerpc64le-linux
Date: Fri, 21 Oct 2022 11:30:19 +0200	[thread overview]
Message-ID: <87fsfh34no.fsf@gnu.org> (raw)
In-Reply-To: <87h6zx8t3e.fsf_-_@gnu.org> ("Ludovic Courtès"'s message of "Fri, 21 Oct 2022 10:43:33 +0200")


Hey,

> How frequently does that machine become unreachable?
>
> Its uptime right now is “only” 51 days, but it seems to have been
> reliably building things so far (surprisingly so!).

Oh so it must be available from the Cuirass point of view but not from
the guix offload point of view. I'll try to fix it today.

> In Cuirass, we should arrange to support partial evaluations or
> per-system evaluations so that a single missing offload machine doesn’t
> cause the whole evaluation to fail.

We can define a guix specification for x86_64-linux, i686-linux and
aarch64-linux and a different one for powerpc64le-linux. That can be
done really quickly. That can break some mechanisms relying on the fact
that the guix specification name is "guix" though.

> That’s radical, but maybe that’s the most reasonable option.
>
> How about a plan like this: until next Thursday, we try to address the
> infrastructure issues discussed above to estimate feasibility.  Then we
> decide on the way forward.  WDYT?

Alright, let's try that :). I agree that it is a pity not to release for
those architectures but on the other hand, we cannot offer fresh
substitutes reliably for them.

The recent outages of ci.guix.gnu.org have shown once again that the
infrastructure is maybe one of the most important Guix aspect. Without
it, Guix is almost unusable, in particular on architectures for which
it's hard to find powerful hardware.

Given the limited amount of people willing to help for
powerpc64le-linux and armhf-linux and the limited amount of hardware
resources available for those, I think it could be reasonable to focus
on a smaller set of architectures and provide stronger guarantees on
those in term of substitutes availability.

But let's discuss that again next week depending on our progress.

Thanks,

Mathieu


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

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06 14:50 Planning for a release, for real Ludovic Courtès
2022-10-06 16:02 ` Julien Lepiller
2022-10-07  9:49   ` Ludovic Courtès
2022-10-07 10:14     ` Julien Lepiller
2022-10-06 16:07 ` Maxime Devos
2022-10-07  9:50   ` Ludovic Courtès
2022-10-07  9:53     ` Maxime Devos
2022-10-07  6:20 ` Supported architectures Efraim Flashner
2022-10-07 10:02   ` Ludovic Courtès
2022-10-07 14:24   ` [bug#58357] [Patch staging ] doc add a recommended system in 'Hardware Considerations' Joshua Branson via Guix-patches via
2022-10-08  9:55     ` pelzflorian (Florian Pelz)
2022-10-08 15:33     ` jbranso--- via Guix-patches via
2022-10-10 10:07       ` pelzflorian (Florian Pelz)
2022-10-14 15:12         ` Ludovic Courtès
2022-10-14 15:47           ` kiasoc5 via Guix-patches via
2022-10-15  9:47             ` pelzflorian (Florian Pelz)
2022-10-16 11:53               ` pelzflorian (Florian Pelz)
2022-10-14 17:09           ` pelzflorian (Florian Pelz)
2022-10-15 15:51             ` pelzflorian (Florian Pelz)
2022-10-17 16:35             ` Ludovic Courtès
2022-10-14 19:28           ` jbranso--- via Guix-patches via
2022-11-03 19:21           ` Ludovic Courtès
2022-11-16  0:22     ` pelzflorian (Florian Pelz)
2022-11-16 23:16       ` jbranso--- via Guix-patches via
2022-11-17 16:26         ` pelzflorian (Florian Pelz)
2022-11-19 14:06           ` Joshua Branson via Guix-patches via
2022-12-08 17:02             ` pelzflorian (Florian Pelz)
2023-03-09 21:06       ` pelzflorian (Florian Pelz)
2023-08-20 17:44         ` pelzflorian (Florian Pelz)
2022-10-10  7:57   ` Supported architectures Csepp
2022-10-12 20:40   ` Vagrant Cascadian
2022-10-13 15:06     ` Ludovic Courtès
2022-10-07  8:26 ` Planning for a release, for real Christopher Baines
2022-10-07 10:09   ` Ludovic Courtès
2022-10-10 10:33 ` zimoun
2022-10-13 15:19 ` Release progress, week 1 Ludovic Courtès
2022-10-13 15:33   ` Efraim Flashner
2022-10-13 15:42   ` Christopher Baines
2022-10-20 13:49   ` Release progress, week 2 Ludovic Courtès
2022-10-20 20:07     ` Efraim Flashner
2022-10-21  8:51       ` Rust on aarch64-linux Ludovic Courtès
2022-10-21 13:42         ` Efraim Flashner
2022-10-22 20:22         ` Efraim Flashner
2022-10-26  9:01           ` Efraim Flashner
     [not found]     ` <87h6zyo811.fsf@gnu.org>
2022-10-21  8:43       ` Status of armhf-linux and powerpc64le-linux Ludovic Courtès
2022-10-21  9:30         ` Mathieu Othacehe [this message]
2022-10-31 17:40         ` Tobias Platen
2022-10-22 12:18     ` Release progress, week 2 Christopher Baines
2022-10-25  9:50     ` Release progress, week 2, release manifest, what builds are failing? Christopher Baines
2022-10-25 11:29       ` Release progress, week 2, release manifest, what builds are failing: gst-plugins-bad Christopher Baines

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fsfh34no.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.