[SciPy-Dev] [SciPy-User] ANN: scipy 0.8.0 release candidate 3

[Derek Homeier]

On 15.07.2010, at 11:15PM, Vincent Davis wrote:

> Looks good for me now running py2.7 on oxs compiled 64bit
> 
> Ran 4407 tests in 119.221s
> OK (KNOWNFAIL=19, SKIP=35)
> <nose.result.TextTestResult run=4407 errors=0 failures=0>
> 

Notably, I never got trouble-free builds with 2.7 - both the numpy and scipy test suites fail 
with a bus error - I already tried compiling with gcc 4.2 instead of 4.0, but to no avail. 
That said, numpy and scipy, as well as matplotlib and a number of other packages do 
run in everyday operations without any failures so far. 

With python2.5/2.6 I've found only two problems on MacOS X 10.5/PPC (already present in 
rc1 and rc2, sorry I did not get around to report them earlier):

I.
======================================================================
ERROR: test_wavfile.test_read_1
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/sw/lib/python2.6/site-packages/nose/case.py", line 186, in runTest
    self.test(*self.arg)
  File "/sw/lib/python2.6/site-packages/scipy/io/tests/test_wavfile.py", line 14, in test_read_1
    rate, data = wavfile.read(datafile('test-44100-le-1ch-4bytes.wav'))
  File "/sw/lib/python2.6/site-packages/scipy/io/wavfile.py", line 124, in read
    return rate, data
UnboundLocalError: local variable 'data' referenced before assignment

I noted there already is a fix for big-endian architectures in 
http://projects.scipy.org/scipy/changeset/5575

though I don't quite understand how it is supposed to work since _big_endian = False is still hardcoded. 

test-8000-le-2ch-1byteu.wav loads without errors anyway, 
but even when setting _big_endian = True manually, both files fail with a 
/sw/lib/python2.6/site-packages/scipy/io/wavfile.py in read(file)
    119         else:
    120             warnings.warn("chunk not understood", WavFileWarning)
--> 121             size = struct.unpack('I',fid.read(4))[0]
    122             bytes = fid.read(size)
    123     fid.close()

error: unpack requires a string argument of length 4

- sorry I can't be of more help with this. 

II.
======================================================================
FAIL: test_data.test_boost(<Data for gamma: test_gamma_data_ipp-near_m55>,)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/sw/lib/python2.6/site-packages/nose/case.py", line 186, in runTest
    self.test(*self.arg)
  File "/sw/lib/python2.6/site-packages/scipy/special/tests/test_data.py", line 205, in _test_factory
    test.check(dtype=dtype)
  File "/sw/lib/python2.6/site-packages/scipy/special/tests/testutils.py", line 223, in check
    assert False, "\n".join(msg)
AssertionError: 
Max |adiff|: 5.56451e-80
Max |rdiff|: 6.01399e-12
Bad results for the following points (in output 0):
                        -55.25 =>          1.281342652143248e-73 !=         1.2813426521356121e-73  (rdiff         5.9592794108831318e-12)
                      -55.0625 =>         9.8673260749254454e-73 !=         9.8673260748719804e-73  (rdiff         5.4183854671083142e-12)
                    -55.015625 =>          4.736069454765531e-72 !=         4.7360694547400013e-72  (rdiff         5.3904770710359471e-12)

[remaining results skipped, all with 4.6e-12 < rdiff < 6.1e-12]
I'd say just another case of too strict accuracy requirements. 


scipy.test('full') in addition produces the following failure on PPC:

======================================================================
FAIL: test_iv_cephes_vs_amos_mass_test (test_basic.TestBessel)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/sw/lib/python2.6/site-packages/scipy/special/tests/test_basic.py", line 1621, in test_iv_cephes_vs_amos_mass_test
    assert dc[k] < 1e-9, (v[k], x[k], iv(v[k], x[k]), iv(v[k], x[k]+0j))
AssertionError: (-1.685450377317264, 1.2676128629915242, 4.748141012443594e-05, (4.7481418802688318e-05+0j))

Both standard and full test pass on i386 and x86_64, but I noticed the following strange behaviour: 
when running the test suite twice in a row, the second run produces these failures: 

======================================================================
FAIL: test_mio.test_mat4_3d(<type 'exceptions.DeprecationWarning'>, <functools.partial object at 0x33c66f0>, <StringIO.StringIO instance at 0x4d542b0>, {'a': array([[[ 0,  1,  2,  3],
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/sw/lib/python2.6/site-packages/nose/case.py", line 186, in runTest
    self.test(*self.arg)
  File "/sw/lib/python2.6/site-packages/numpy/testing/utils.py", line 973, in assert_raises
    return nose.tools.assert_raises(*args,**kwargs)
AssertionError: DeprecationWarning not raised

======================================================================
FAIL: test_00_deprecation_warning (test_basic.TestSolveHBanded)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/sw/lib/python2.6/site-packages/scipy/linalg/tests/test_basic.py", line 261, in test_00_deprecation_warning
    assert_raises(DeprecationWarning, solveh_banded, ab, b)
  File "/sw/lib/python2.6/site-packages/numpy/testing/utils.py", line 973, in assert_raises
    return nose.tools.assert_raises(*args,**kwargs)
AssertionError: DeprecationWarning not raised

======================================================================
FAIL: Regression test for #651: better handling of badly conditioned
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/sw/lib/python2.6/site-packages/scipy/signal/tests/test_filter_design.py", line 34, in test_bad_filter
    raise AssertionError("tf2zpk did not warn about bad "\
AssertionError: tf2zpk did not warn about bad coefficients

Cheers,
								Derek