all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kaelyn <kaelyn.alexi@protonmail.com>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: i686 core-updates failure.
Date: Fri, 14 Apr 2023 20:05:46 +0000	[thread overview]
Message-ID: <prc6t38rRS978UP6lK2a33l8ecUEjC1swszGWwVZ8yXEMwQWWSgGd1rkGctT7UXHS6pz4uizPXuQtI-Zk5G0uI-IA9RZi8klJ6v18ve6jlA=@protonmail.com> (raw)
In-Reply-To: <ZDkOtWU5PinGHQEo@jurong>

------- Original Message -------
On Friday, April 14th, 2023 at 8:28 AM, Andreas Enge <andreas@enge.fr> wrote:


> 
> 
> Am Thu, Apr 13, 2023 at 06:25:47PM +0200 schrieb Andreas Enge:
> 
> > For the Fortran bindings, I am hesitant as well. I think it is bad style
> > to disable a test just because it fails ;-) Maybe someone with experience
> > in numpy can speak up.
> 
> 
> Well, given how many packages on i686 eventually depend on numpy,
> I think disabling these two tests on i686 (maybe in a phase so that they
> continue to run on other architectures, see the recent powerpc commit on
> core-updates) is justifiable. At worst we end up with numpy with broken
> fortran bindings on i686. It is likely that pulseaudio will continue
> to work nevertheless.

I just sent in https://issues.guix.gnu.org/62843 to disable the two tests for i686 and armhf (disabling TestKind.test_all for armhf might not be needed, but the Gentoo package definition suggests the huge array test will fail for armhf as well).

Cheers,
Kaelyn

> 
> Andreas


  reply	other threads:[~2023-04-14 20:06 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 16:11 i686 core-updates failure Kaelyn
2023-04-12 21:05 ` Josselin Poiret
2023-04-12 21:31 ` Andreas Enge
2023-04-13  4:37   ` Kaelyn
2023-04-13 16:25     ` Andreas Enge
2023-04-14  8:28       ` Andreas Enge
2023-04-14 20:05         ` Kaelyn [this message]
2023-04-15 11:20           ` python-pytest on core-updates (was: i686 core-updates failure.) Andreas Enge
2023-04-15 11:32             ` python-pytest on core-updates Andreas Enge
2023-04-15 14:08               ` [PATCH core-updates] gnu: python-pytest: Fix failing test_raising_repr Josselin Poiret
2023-04-15 16:14                 ` Kaelyn
2023-04-15 19:59                 ` Andreas Enge
2023-04-15 20:47                   ` Andreas Enge
2023-04-15 20:49             ` python-pytest on core-updates (was: i686 core-updates failure.) Andreas Enge
2023-04-13  9:18 ` i686 core-updates failure Simon Tournier
2023-04-13 13:23 ` jgart
2023-04-13 13:43   ` Andreas Enge
2023-04-14 15:12     ` Csepp
2023-04-14 16:58       ` Simon Tournier
2023-04-14 17:30         ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-04-13 15:31   ` Simon Tournier
2023-04-13 16:21     ` Simon Tournier
2023-04-13 15:47   ` Ricardo Wurmus
2023-04-13 16:15     ` Greg Hogan
2023-04-13 16:39     ` Simon Tournier
2023-04-13 16:47       ` Ricardo Wurmus
2023-04-13 20:02       ` Lars-Dominik Braun
2023-04-13 20:15         ` Simon Tournier
2023-04-13 20:45           ` Andreas Enge
2023-04-13 20:57             ` Simon Tournier
2023-04-14  8:25               ` Andreas Enge
2023-04-14  9:45                 ` Simon Tournier
2023-04-14 18:16                 ` Andreas Enge
2023-04-14 18:40                   ` Lars-Dominik Braun
2023-04-15  9:48                     ` ghc in core-updates on i686 Andreas Enge
2023-04-14 10:49           ` i686 core-updates failure Lars-Dominik Braun
2023-04-14 17:00             ` Simon Tournier
2023-04-13 20:33 ` wget (was Re: i686 core-updates failure.) Simon Tournier
2023-04-13 20:37   ` Andreas Enge
2023-04-13 20:43     ` Simon Tournier
2023-04-13 20:49       ` wget Andreas Enge
2023-04-15  0:51   ` wget (was Re: i686 core-updates failure.) Maxim Cournoyer
2023-04-15 10:43     ` Andreas Enge
2023-04-15 16:37       ` Kaelyn
2023-04-15 18:25         ` Kaelyn
2023-04-15 21:00           ` wget on i686 in core-updates Andreas Enge
2023-04-16 17:06           ` wget (was Re: i686 core-updates failure.) Andreas Enge
2023-04-16 17:49             ` Kaelyn

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='prc6t38rRS978UP6lK2a33l8ecUEjC1swszGWwVZ8yXEMwQWWSgGd1rkGctT7UXHS6pz4uizPXuQtI-Zk5G0uI-IA9RZi8klJ6v18ve6jlA=@protonmail.com' \
    --to=kaelyn.alexi@protonmail.com \
    --cc=andreas@enge.fr \
    --cc=guix-devel@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.