I'm seeing these three failures on Solaris 5.10 (x86_64, using Python 2.7.1):
======================================================================
FAIL: Test basic arithmetic function errors
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/home/demo/master/lib/python2.7/site-packages/numpy/testing/decorators.py",
line 215, in knownfailer
return f(*args, **kwargs)
File
"/home/demo/master/lib/python2.7/site-packages/numpy/core/tests/test_numeric.py",
line 321, in test_floating_exceptions
lambda a,b:a/b, ft_tiny, ft_max)
File
"/home/demo/master/lib/python2.7/site-packages/numpy/core/tests/test_numeric.py",
line 271, in assert_raises_fpe
"Type %s did not raise fpe error '%s'." % (ftype, fpeerr))
File "/home/demo/master/lib/python2.7/site-packages/numpy/testing/utils.py",
line 34, in assert_
raise AssertionError(msg)
AssertionError: Type <type 'numpy.float32'> did not raise fpe error 'underflow'.
======================================================================
FAIL: test_zero_nzero (test_umath.TestArctan2SpecialValues)
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/home/demo/master/lib/python2.7/site-packages/numpy/core/tests/test_umath.py",
line 322, in test_zero_nzero
assert_almost_equal(ncu.arctan2(np.PZERO, np.NZERO), np.pi)
File "/home/demo/master/lib/python2.7/site-packages/numpy/testing/utils.py",
line 468, in assert_almost_equal
raise AssertionError(msg)
AssertionError:
Arrays are not almost equal to 7 decimals
ACTUAL: 0.0
DESIRED: 3.141592653589793
======================================================================
FAIL: test_zero_pzero (test_umath.TestArctan2SpecialValues)
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/home/demo/master/lib/python2.7/site-packages/numpy/core/tests/test_umath.py",
line 328, in test_zero_pzero
assert_arctan2_isnzero(np.NZERO, np.PZERO)
File
"/home/demo/master/lib/python2.7/site-packages/numpy/core/tests/test_umath.py",
line 310, in assert_arctan2_isnzero
assert (ncu.arctan2(x, y) == 0 and np.signbit(ncu.arctan2(x, y))),
"arctan(%s, %s) is %s, not -0" % (x, y, ncu.arctan2(x, y))
AssertionError: arctan(-0.0, 0.0) is 0.0, not -0
----------------------------------------------------------------------
Ran 3152 tests in 16.990s
I'm not sure what the state of Solaris support is these days, but
I remember being able to run all tests without any failures.
- Ilan
On Tue, May 3, 2011 at 4:06 PM, Ralf Gommers
<ralf.gomm...@googlemail.com> wrote:
> On Tue, May 3, 2011 at 10:35 PM, Christoph Gohlke <cgoh...@uci.edu> wrote:
>>
>>
>> On 5/3/2011 11:18 AM, Ralf Gommers wrote:
>>> Hi,
>>>
>>> I am pleased to announce the availability of the second release
>>> candidate of NumPy 1.6.0.
>>>
>>> Compared to the first release candidate, one segfault on (32-bit
>>> Windows + MSVC) and several memory leaks were fixed. If no new
>>> problems are reported, the final release will be in one week.
>>>
>>> Sources and binaries can be found at
>>> http://sourceforge.net/projects/numpy/files/NumPy/1.6.0rc2/
>>> For (preliminary) release notes see below.
>>>
>>> Enjoy,
>>> Ralf
>>>
>>
>> Looks good. The msvc9/MKL builds now pass all tests on win32 and
>> win-amd64, python 2.6, 2.7, 3.1, and 3.2.
>
> Good, thanks for testing.
>>
>> One scipy test failure reported earlier remains, but that is probably no
>> release blocker.
>> <http://mail.scipy.org/pipermail/numpy-discussion/2011-April/055877.html>
>
> That's a problem in scipy.stats, that only showed up recently because
> of a bug fix in numpy.testing.
>
> Cheers,
> Ralf
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>
_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
