[SciPy-User] Testing scipy: a curiosity (Ralf Gommers)

Sergio Rojas sergio_r@mail....
Fri Apr 27 06:27:31 CDT 2012

On Fri, Apr 20, 2012 at 6:53 PM, Sergio Rojas <sergio_r@mail.com> wrote: > > Hello all, > > > Running the scipy tests in sequence: > > scipy.test() > then, after the previous test finished without errors > or failures I run: > scipy.test('full') > some tests fails (see below). > > Exiting and starting a new python session and > executing only the test suite: > > scipy.test('full') > > No failures or errors are reported. The test ends with: > ... > ---------------------------------------------------------------------- > Ran 5832 tests in 423.039s > OK (KNOWNFAIL=14, SKIP=42) > <nose.result.TextTestResult run=5832 errors=0 failures=0> > > What could be the problem?. Can we trust these tests results? > Python's default behavior is to raise warnings from the same place in the code only once. So when you re-run the tests it doesn't raise those warnings. The tests check that a warning is raised. Hence the failures. Ralf Thanks for replying, Ralf. A natural questions then raises Ralf, Can one obtain fictitious python's error messages or failures of a computation because of such python's default behavior? How can we toggle that to a most reasonable behavior? or how can we associate an error or failure (what hint can we have from the system) to such behavior? Sergio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/scipy-user/attachments/20120427/1ccc4026/attachment.html 

More information about the SciPy-User mailing list