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

Hi Ludo’!

Em quarta-feira, 4 de agosto de 2021, às 17:48:59 -03, Ludovic Courtès 
escreveu:
> Thiago Jung Bauermann <bauermann@kolabnow.com> skribis:
> > Em quarta-feira, 28 de julho de 2021, às 08:50:16 -03, Mathieu Othacehe
> 
> > escreveu:
> [...]
> 
> >> Cuirass has started evaluating this branch here:
> >> https://ci.guix.gnu.org/jobset/core-updates-frozen. According to the
> >> related dashboard, there's still a bit of work required to stabilize
> >> this branch: https://ci.guix.gnu.org/eval/68124/dashboard.
> > 
> > There are no results for powerpc64le-linux. Does anyone know why?
> 
> It was turned off in the config at
> <https://ci.guix.gnu.org/specification/edit/core-updates-frozen>.  I’ve
> added it now (though maybe it won’t actually build until someone has
> pushed.)

Thanks for the explanation. And thanks for re-adding it!

> 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!

> (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.

> > The last Cuirass evaluation of core-updates with powerpc64le-linux
> > results is https://ci.guix.gnu.org/eval/67285 so I tried to run the
> > failed builds on my VM to see what the current state is. My
> > core-updates-frozen branch was at commit f8458a228224
> > (”build-system/python: Handle missing metadata on Python 2.”) when I
> > did these builds.
> > 
> > At first, I didn’t try the “*tarball*” builds because I didn’t want to
> > focus on the bootstrap binaries. Apart from those, I was glad to see
> > that all failed powerpc64le-linux builds from that evaluation built
> > fine on my VM, except for the ones below:
> > 
> > • gcc-toolchain@4.8
> > • gcc-toolchain@5.5
> > • gmp@4.3.2 aka `(@@ (gnu packages commencement) gmp-boot)`
> > • mpfr@2.4.2 aka `(@@ (gnu packages commencement) mpfr-boot)`
> > • mpc@1.0.3 aka `(@@ (gnu packages commencement) mpc-boot)`
> > 
> > I later tried building ‘bootstrap-tarballs’, but it failed during the
> > build of the static gawk binary.
> > 
> > I also did a `guix pull --branch=core-updates-frozen`, which built a
> > ton of stuff and completed successfully. At the time,
> > core-updates-frozen was at commit 5e4cdb5b3b1d (”gnu: python-django:
> > Fix test failure.”)
> 
> Woow, that’s fairly intense testing!

:-)

I was glad to see that powerpc64le-linux was in better shape than I had 
thought.

> Does the Coreutils test failure at <https://issues.guix.gnu.org/49752>
> happen on real hardware?

Thanks for point it out. I just tested and it doesn’t! I’ll close that 
issue.

> > 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. :-)

-- 
Thanks,
Thiago




  reply	other threads:[~2021-08-04 23:05 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 [this message]
2021-08-11 10:18       ` Ludovic Courtès
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=1972598.aYIYqKt5Vz@popigai \
    --to=bauermann@kolabnow.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).