Hi Étienne,
Am Sun, Jan 29, 2023 at 09:19:44PM +0100 schrieb Étienne Mollier:
> The uname machine name may not have been armv7l on the test bed,
> leading to the present crash. This should read like the below
> and I consider pushing a "fix" in that direction tomorrow:
>
>
Hi Andreas,
Andreas Tille, on 2023-01-29:
> Any idea what might be wrong here?
The nibabel 5.0.0-1 migration log[2] and architecture memo[3]
show that I have been too strict for my test skipping heuristic:
___ test_a2f_nan2zero_range
Hi,
the according log[1] says:
=== FAILURES ===
___ test_a2f_nan2zero_range
def test_a2f_nan2zero_range():
# array_to_file should check if nan can be represented as
Control: reopen -1
autopkgtests of nibabel/5.0.0-1 still fail in the same way on armel.
https://ci.debian.net/packages/n/nibabel/testing/armel/
Source: nibabel
Version: 4.0.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: needs-update
Hi Maintainer
The autopkgtests of nibabel fail with NumPy 1.24 on armel [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1]
5 matches
Mail list logo
