-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.9.0 system test failures #3165
Comments
Thank you for this report @mr-c. We need to block time to focus on this. We also need to add a CI to catch this earlier. |
Thank you for the update @skoudoro We now see the first error ( Do you know when you might block time for this? |
Regarding the 32-bit failure:
4 GiB is the fundamental address space limit on 32-bit architectures, you cannot address more than 2^32 bytes there. In practice 32-bit architectures have between 2 GiB and 4 GiB address space. If this is not the only place in the testcase where an array with over 100 million 8 byte variables is being allocated, then that test is too large for 32-bit architectures. |
Description
In Debian, we are seeing two test failures for dipy 1.9.0 on 32-bit systems, including x86:
1.
Full i386 (really i686) build log: https://buildd.debian.org/status/fetch.php?pkg=dipy&arch=i386&ver=1.9.0-1&stamp=1711634908&raw=0
Way to reproduce
Here's a Dockerfile:
[If reporting a bug, please include the following important information:]
python -c "import platform; print(platform.platform())"
):Linux-6.1.0-18-amd64-x86_64-with-glibc2.37
python -c "import sys; print('Python', sys.version)"
):Python 3.12.2 (main, Mar 26 2024, 12:39:01) [GCC 13.2.0]
python -c "import dipy; print(dipy.__version__)"
): 1.9.0NumPy 1.26.4
SciPy 1.11.4
Nibabel 5.2.1
H5py 3.10.0
No module named 'cvxpy'
No module named 'fury
The text was updated successfully, but these errors were encountered: