Hope this is the right list to post this problem! I'm getting two errors when running a numpy (see below). Could someone tell me how to fix this or if the errors are not a concern. Dwayne python -c 'import numpy; numpy.test(verbose=2)' Python 2.7.3 Numpy 1.6.2 Nose 1.1.2 PowerPC Red Hat Linux 64 bit ====================================================================== FAIL: test_umath.test_nextafterl ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/local/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/local/lib/python2.7/site-packages/numpy/testing/decorators.py", line 215, in knownfailer return f(*args, **kwargs) File "/usr/local/lib/python2.7/site-packages/numpy/core/tests/test_umath.py", line 1119, in test_nextafterl return _test_nextafter(np.longdouble) File "/usr/local/lib/python2.7/site-packages/numpy/core/tests/test_umath.py", line 1103, in _test_nextafter assert np.nextafter(one, two) - one == eps AssertionError ====================================================================== FAIL: test_umath.test_spacingl ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/local/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/local/lib/python2.7/site-packages/numpy/testing/decorators.py", line 215, in knownfailer return f(*args, **kwargs) File "/usr/local/lib/python2.7/site-packages/numpy/core/tests/test_umath.py", line 1146, in test_spacingl return _test_spacing(np.longdouble) File "/usr/local/lib/python2.7/site-packages/numpy/core/tests/test_umath.py", line 1128, in _test_spacing assert np.spacing(one) == eps AssertionError ---------------------------------------------------------------------- Ran 3576 tests in 22.974s FAILED (KNOWNFAIL=6, failures=2)
Disclosure: I'm not a numpy developer You've certainly got a functional numpy installation if those are the only two tests failing. Those two tests are related to the distance between floating-point numbers using long double precision (128 bits). If you're not using long doubles, then you probably don't need to worry about them. Still, the developers are interested in tests failing on non-x86 corner cases like this so thanks for reporting. -Aron
Good information to know Aron which I'll pass on to the group. Lets also see what the developers have to say since I'm hoping they watch this distribution list. Dwayne ________________________________________ From: Aron Ahmadia [aron@ahmadia.net] Sent: Friday, July 06, 2012 7:36 AM To: Discussion of Numerical Python Subject: Re: [Numpy-discussion] Numpy test failure - How to fix Disclosure: I'm not a numpy developer You've certainly got a functional numpy installation if those are the only two tests failing. Those two tests are related to the distance between floating-point numbers using long double precision (128 bits). If you're not using long doubles, then you probably don't need to worry about them. Still, the developers are interested in tests failing on non-x86 corner cases like this so thanks for reporting. -Aron
On Fri, Jul 6, 2012 at 1:30 PM, McCully, Dwayne (NIH/NLM/LHC) [C] < dmccully@mail.nih.gov> wrote:
Hope this is the right list to post this problem! I’m getting two errors when running a numpy (see below). ****
Could someone tell me how to fix this or if the errors are not a concern. ****
** **
Dwayne****
** **
python -c 'import numpy; numpy.test(verbose=2)'****
** **
Python 2.7.3****
Numpy 1.6.2****
Nose 1.1.2****
PowerPC****
Red Hat Linux 64 bit**
These tests are known to fail on PowerPC, see http://projects.scipy.org/numpy/ticket/1664 https://github.com/numpy/numpy/commit/1b99089 The question is why the above commit is not effective on your system. Could you check that? For example, is this not true: import platform "powerpc" in platform.processor() Ralf
**
*======================================================================*
FAIL: test_umath.test_nextafterl****
----------------------------------------------------------------------****
Traceback (most recent call last):****
File "/usr/local/lib/python2.7/site-packages/nose/case.py", line 197, in runTest****
self.test(*self.arg)****
File "/usr/local/lib/python2.7/site-packages/numpy/testing/decorators.py", line 215, in knownfailer****
return f(*args, **kwargs)****
File "/usr/local/lib/python2.7/site-packages/numpy/core/tests/test_umath.py", line 1119, in test_nextafterl****
return _test_nextafter(np.longdouble)****
File "/usr/local/lib/python2.7/site-packages/numpy/core/tests/test_umath.py", line 1103, in _test_nextafter****
assert np.nextafter(one, two) - one == eps****
AssertionError****
** **
======================================================================****
FAIL: test_umath.test_spacingl****
----------------------------------------------------------------------****
Traceback (most recent call last):****
File "/usr/local/lib/python2.7/site-packages/nose/case.py", line 197, in runTest****
self.test(*self.arg)****
File "/usr/local/lib/python2.7/site-packages/numpy/testing/decorators.py", line 215, in knownfailer****
return f(*args, **kwargs)****
File "/usr/local/lib/python2.7/site-packages/numpy/core/tests/test_umath.py", line 1146, in test_spacingl****
return _test_spacing(np.longdouble)****
File "/usr/local/lib/python2.7/site-packages/numpy/core/tests/test_umath.py", line 1128, in _test_spacing****
assert np.spacing(one) == eps****
AssertionError****
** **
----------------------------------------------------------------------****
Ran 3576 tests in 22.974s****
** **
FAILED (KNOWNFAIL=6, failures=2)****
** **
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Hi, On Sun, Jul 8, 2012 at 2:36 AM, Ralf Gommers <ralf.gommers@googlemail.com> wrote:
On Fri, Jul 6, 2012 at 1:30 PM, McCully, Dwayne (NIH/NLM/LHC) [C] <dmccully@mail.nih.gov> wrote:
Hope this is the right list to post this problem! I’m getting two errors when running a numpy (see below).
Could someone tell me how to fix this or if the errors are not a concern.
Dwayne
python -c 'import numpy; numpy.test(verbose=2)'
Python 2.7.3
Numpy 1.6.2
Nose 1.1.2
PowerPC
Red Hat Linux 64 bit
These tests are known to fail on PowerPC, see http://projects.scipy.org/numpy/ticket/1664 https://github.com/numpy/numpy/commit/1b99089
The question is why the above commit is not effective on your system. Could you check that? For example, is this not true:
import platform "powerpc" in platform.processor()
I get this on OSX PPC: In [1]: import platform In [2]: platform.processor() Out[2]: 'powerpc' In [3]: platform.machine() Out[3]: 'Power Macintosh' and this on Debian Wheezy PPC: In [1]: import platform In [2]: platform.processor() Out[2]: '' In [3]: platform.machine() Out[3]: 'ppc' In my own code I ended up making a one-line function, 'on_powerpc': https://github.com/nipy/nibabel/blob/master/nibabel/casting.py#L171 def on_powerpc(): return processor() == 'powerpc' or machine().startswith('ppc') See you, Matthew
On Sun, Jul 8, 2012 at 11:47 AM, Matthew Brett <matthew.brett@gmail.com>wrote:
Hi,
On Sun, Jul 8, 2012 at 2:36 AM, Ralf Gommers <ralf.gommers@googlemail.com> wrote:
On Fri, Jul 6, 2012 at 1:30 PM, McCully, Dwayne (NIH/NLM/LHC) [C] <dmccully@mail.nih.gov> wrote:
Hope this is the right list to post this problem! I’m getting two
errors
when running a numpy (see below).
Could someone tell me how to fix this or if the errors are not a concern.
Dwayne
python -c 'import numpy; numpy.test(verbose=2)'
Python 2.7.3
Numpy 1.6.2
Nose 1.1.2
PowerPC
Red Hat Linux 64 bit
These tests are known to fail on PowerPC, see http://projects.scipy.org/numpy/ticket/1664 https://github.com/numpy/numpy/commit/1b99089
The question is why the above commit is not effective on your system. Could you check that? For example, is this not true:
import platform "powerpc" in platform.processor()
I get this on OSX PPC:
In [1]: import platform
In [2]: platform.processor() Out[2]: 'powerpc'
In [3]: platform.machine() Out[3]: 'Power Macintosh'
and this on Debian Wheezy PPC:
In [1]: import platform
In [2]: platform.processor() Out[2]: ''
In [3]: platform.machine() Out[3]: 'ppc'
In my own code I ended up making a one-line function, 'on_powerpc':
https://github.com/nipy/nibabel/blob/master/nibabel/casting.py#L171
def on_powerpc(): return processor() == 'powerpc' or machine().startswith('ppc')
Thanks Matthew. Sent a PR for this: https://github.com/numpy/numpy/pull/345 Ralf
participants (4)
-
Aron Ahmadia -
Matthew Brett -
McCully, Dwayne (NIH/NLM/LHC) [C] -
Ralf Gommers