[Numpy-discussion] Fresh svn numpy install fails 2 tests (OS X)

David M. Cooke cookedm at physics.mcmaster.ca
Mon Jul 24 16:24:18 CDT 2006


On Sat, 22 Jul 2006 17:50:13 -0400
Steve Lianoglou <lists.steve at arachnedesign.net> wrote:

> Hi folks,
> 
> Since 1.0 release is eminent, I just wanted to draw the attention to  
> two failures I get when I run numpy.test(1).
> 
> I've never been able to get numpy to pass all test cases, but now it  
> fails a second one, so .. I'm pasting it below. Please let me know if  
> these are non-consequential.

It fails the second one b/c I added it because the failure in the first one
wasn't clear enough :-)

> System info:
> 	+ Intel Mac (MacBook Pro)
> 	+ OS X.4.7
> 	+ numpy version: 1.0.2881
> 
> test failures:
> 
> FAIL: check_large_types (numpy.core.tests.test_scalarmath.test_power)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>    File "/opt/local/lib/python2.4/site-packages/numpy/core/tests/ 
> test_scalarmath.py", line 47, in check_large_types
>      assert b == 6765201, "error with %r: got %r" % (t,b)
> AssertionError: error with <type 'float128scalar'>: got 0.0
> 
> ======================================================================
> FAIL: check_types (numpy.core.tests.test_scalarmath.test_types)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>    File "/opt/local/lib/python2.4/site-packages/numpy/core/tests/ 
> test_scalarmath.py", line 20, in check_types
>      assert a == 1, "error with %r: got %r" % (atype,a)
> AssertionError: error with <type 'float128scalar'>: got  
> 1.02604810941480982577e-4936
> 
> ----------------------------------------------------------------------
> Ran 468 tests in 1.157s
> 
> FAILED (failures=2)
> Out[2]: <unittest.TextTestRunner object at 0x15e3510>

I'm aware of this (http://projects.scipy.org/scipy/numpy/ticket/183). It's a
problem on PPC macs also. Travis thinks it may be a compiler problem. I've
had a look, and can't see anything obvious.

It *could* be that somewhere there's a typo in the code where things
are set when sizeof(long double) == 128.

-- 
|>|\/|<
/--------------------------------------------------------------------------\
|David M. Cooke                      http://arbutus.physics.mcmaster.ca/dmc/
|cookedm at physics.mcmaster.ca




More information about the Numpy-discussion mailing list