Your message dated Wed, 19 Jun 2024 10:56:08 +0200
with message-id <0bdd68b4-afb2-4c8a-ba07-6935fb1c3...@debian.org>
and subject line Re: dipy: FTBFS on 32 bit archs with ArrayMemoryError
has caused the Debian Bug report #1071448,
regarding dipy: FTBFS on 32 bit archs with ArrayMemoryError
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1071448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dipy
Version: 1.9.0-2
Severity: serious
Tags: ftbfs
User: debian-rele...@lists.debian.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Dear maintainer,

your package does not build on armhf, armel, and i386 because one tests 
allocates a rather large array (which fails on the buildd machines):


  >       data = 255 * rng.random((197, 233, 189, 15))
  E       numpy.core._exceptions._ArrayMemoryError: Unable to allocate 993. 
  MiB for an array with shape (197, 233, 189, 15) and data type float64


Cheers
Timo


-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmwPruYMA35fCsSO/zIxr3RQD9MoFAmZKAkUACgkQzIxr3RQD
9Moqnw//QjkAG+RG9VH78jKUefxRe2eNmmH/zSChSdTAMzit4UrY/TcFgP1H/nIF
ZhbsjlDPNvu3Wxsf7zLORHgN+trRV69Na3RLECKqxb+ImHIShMZKPd3IYKcKRPC/
XysUUGozWSixnNiD+PfhK8Eo2kh4odpwz9WiygAy0cH0oVGP+S6z6y7/BkKDjrxE
45aVDrCCDcbjsSoXOrGh6AIEYQxQ27sxoLptU+M2fS1WMd+TWmnQ3J4rJSf/0psa
SetJ2Vm87kdgfIvPLjYY7XmFJ6dTcalt54Z0KTLQfBb0fO81THPDKm5AJX0dtimy
QMCSDQYh9j+HO5LmhR3y4bswf3jxrDDCeOQ21QXln+UVG/q+nDjtQIwWyA6cj6za
V9T2ERS5e+eMK13VkxVHLE3SEy/bwhoctj271m2370pLI6guYeLMO5bMdoeikyFg
voH3peV08RWz22wOfymX3DK8DmcwWUDcQf8BVIv5MAv8mWVVaqzUnn5pt4o4h5aL
Ul9WgFaGoCLi+Sp0VSIsFzQEzrO4hWRB+RaDeaAklRHTeAdSjg+/9959j36ZwkIy
A2bDtVWtAEhYEuNj3LUUjzs0OR8gu4uTdt6Tjpb0HM2jSL3CyiIddLs+tw1Fe7ev
GweUn20QAa3HF40GfWXaUS75pwap2BpyG5IQcyjWtD7W7ihDIbY=
=SYkm
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message ---
Version: 1.9.0-4

This was fixed in the latest release

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to