You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inside the manylinux2010 i686 docker, log(-1) returns nan, but it is a different nan than the one expected by the data used in test_umath_accuracy. The tests expect 0xffc00000, but the glibc log() function on this platform returns 0x7fc00000. Both are nan, but assert_array_max_ulp uses nulp_diff which is very literal:
>>> import numpy as np, numpy.testing
>>> x = np.int32(0xffc00000).view(np.float32)
>>> y = np.int32(0x7fc00000).view(np.float32)
>>> print(x, y)
nan nan
>>> numpy.testing._private.utils.nulp_diff(y, x)
8388608.0
np.isnan returns True for both.
I think the test be relaxed to accept more than one nan.
The text was updated successfully, but these errors were encountered:
Inside the manylinux2010 i686 docker,
log(-1)
returnsnan
, but it is a differentnan
than the one expected by the data used intest_umath_accuracy
. The tests expect0xffc00000
, but the glibclog()
function on this platform returns0x7fc00000
. Both arenan
, butassert_array_max_ulp
usesnulp_diff
which is very literal:np.isnan
returns True for both.I think the test be relaxed to accept more than one
nan
.The text was updated successfully, but these errors were encountered: