From: Andreas Enge <andreas@enge.fr>
To: Kaelyn <kaelyn.alexi@protonmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: i686 core-updates failure.
Date: Thu, 13 Apr 2023 18:25:47 +0200 [thread overview]
Message-ID: <ZDgtCw/Sj5HmsO3d@jurong> (raw)
In-Reply-To: <ZGtiSjwU2qEqermuQnPV1QQMcRLZXYGK60LCiV4pY2CblY2TmDjzUmZmt56os2_v1QtN7IWYGcAfLNEGZ3DVyEboL5OIcoiBZ9Fdw17sLfs=@protonmail.com>
Hello,
Am Thu, Apr 13, 2023 at 04:37:55AM +0000 schrieb Kaelyn:
> I forgot to mention that I had also tried updating to the latest numpy (2.24.2), with the same tests failing. I agree the test failures in numpy need to be resolved in some way for merging core-updates, since the failure affects such a large number of common (desktop) applications on i686. My inclination is to disable both failing tests (at least for now), and possibly updating to the latest numpy since changing the package would trigger a rebuild anyway. I only hesitate about disabling TestKind.test_all since I don't know what role the Fortran bridging code plays in numpy and if the failure is a sign of a legitimate problem instead of a platform limitation (as the large array test failure seems to be).
I agree with your analysis: I am not overly shocked that on a 32 bit
architecture creating an array of 2^31 elements fails, while on a
64 bit architecture the same test passes. Still, how about sending
a bug report? Can anything be seen from the Debian package? If it is
a consistent 32 bit failure, it had better be repaired upstream.
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.
Andreas
next prev parent reply other threads:[~2023-04-13 16:26 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 [this message]
2023-04-14 8:28 ` Andreas Enge
2023-04-14 20:05 ` Kaelyn
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
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=ZDgtCw/Sj5HmsO3d@jurong \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=kaelyn.alexi@protonmail.com \
/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).