unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Thiago Jung Bauermann <bauermann@kolabnow.com>
Cc: guix-devel <guix-devel@gnu.org>, Mathieu Othacehe <othacehe@gnu.org>
Subject: Re: core-updates-frozen on powerpc64le-linux
Date: Wed, 11 Aug 2021 12:18:27 +0200	[thread overview]
Message-ID: <874kbwp9n0.fsf@gnu.org> (raw)
In-Reply-To: <1972598.aYIYqKt5Vz@popigai> (Thiago Jung Bauermann's message of "Wed, 04 Aug 2021 20:04:42 -0300")

Hi!

Thiago Jung Bauermann <bauermann@kolabnow.com> skribis:

> Em quarta-feira, 4 de agosto de 2021, às 17:48:59 -03, Ludovic Courtès 
> escreveu:
>> Thiago Jung Bauermann <bauermann@kolabnow.com> skribis:

[...]

>> Note that currently ci.guix only does emulated powerpc64le-linux because
>> the only POWER9 machine we currently have access to (lent by OSUOSL) is
>> not running ‘cuirass-remote-worker’.
>
> Ah, I didn’t realise that. I started out my investigations of powerpc64le-
> linux CI failures using emulation on my laptop (both with qemu-user and 
> qemu-system), and found it to be a bit unreliable. I saw some failures in 
> packages’ testsuite results which don’t happen on real hardware. There was 
> one in the glib package in particular which happened on the master branch 
> and prevented a `guix pull` command from succeeding. This is what prompted 
> me to request the Minicloud VM instance.
>
>> It’s a foreign distro (Debian) so
>> setting up these things can be a bit tedious.  If you or anyone would
>> like to help with this, we can discuss it!
>
> I’d be glad to help set that up and maintain the OSUOSL machine!

Excellent!  I think Mathieu, Tobias, and guix-sysadmin@gnu.org should be
able to get you started.  Could you send us an account name and SSH
public key?

>> (bordeaux.guix does have a POWER9 build machine behind, but it’s not
>> building ‘core-updates-frozen’ currently.)
>
> Nice! I’d be glad to help with that machine as well if there’s anything to 
> do on that front.

I think it’s running fine, using the Guix Build Coordinator instead of
Cuirass, set up by Christopher Baines (this POWER9 machine is Chris’s,
currently).

>> > So next step for me is to look into the build failures above. I’ll
>> > semi-randomly start with ‘gmp-boot’ and see what I can find out.
>> 
>> Neat, thank you!
>
> You’re welcome. Patches on issues 49880, 49881 and 49882. :-)

Alrighty, I’ll take a look!

Thanks,
Ludo’.


  reply	other threads:[~2021-08-11 10:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 11:50 Core updates frozen Mathieu Othacehe
2021-08-03 20:15 ` core-updates-frozen on powerpc64le-linux (was: Core updates frozen.) Thiago Jung Bauermann
2021-08-04 20:48   ` core-updates-frozen on powerpc64le-linux Ludovic Courtès
2021-08-04 23:04     ` Thiago Jung Bauermann
2021-08-11 10:18       ` Ludovic Courtès [this message]
2021-08-11 18:45         ` Thiago Jung Bauermann
2021-08-17 12:40 ` Core updates frozen zimoun
2021-08-18 10:33   ` Efraim Flashner
2021-08-20  9:49     ` zimoun
2021-08-20 10:14       ` Efraim Flashner
2021-08-20 19:10       ` Leo Famulari
2021-08-20 21:05         ` core-updates weather reports! Leo Famulari
2021-08-20 21:40           ` Julien Lepiller
2021-08-20 23:08             ` Leo Famulari
2021-08-20 23:25               ` Julien Lepiller
2021-08-20 23:33                 ` Leo Famulari
2021-08-21  0:23                   ` Leo Famulari
2021-08-21  0:30                     ` Leo Famulari
2021-08-21  6:53                     ` Mathieu Othacehe
2021-08-21 21:21                       ` Leo Famulari
2021-08-22  8:19                         ` Mathieu Othacehe
2021-08-21  0:57           ` zimoun
2021-08-21 21:22             ` Leo Famulari
2021-08-22  8:27             ` Mathieu Othacehe
2021-08-30 22:35               ` Ludovic Courtès
2021-08-31  9:11                 ` Mathieu Othacehe

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=874kbwp9n0.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bauermann@kolabnow.com \
    --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).