Re: [Numpy-discussion] numpy.test('full') errors and failures

On Tue, Feb 12, 2013 at 1:28 PM, Daπid wrote: > On 12 February 2013 10:55, Dominic Steinitz wrote: > > Running unit tests for numpy > > NumPy version 1.8.0.dev-4600b2f > > I can see this is not the stable version, try the 1.7 that has been > just released. Sending the full output of this test

Re: [Numpy-discussion] numpy.test('full') errors and failures

On 12 February 2013 10:55, Dominic Steinitz wrote: > Running unit tests for numpy > NumPy version 1.8.0.dev-4600b2f I can see this is not the stable version, try the 1.7 that has been just released. ___ NumPy-Discussion mailing list NumPy-Discussion@sci

[Numpy-discussion] numpy.test('full') errors and failures

Apologies if this is the wrong mailing list. I have installed bumpy using the excellent script here: http://fonnesbeck.github.com/ScipySuperpack/ I ran numpy.test('full') and got several errors. Should I be worried? Thanks, Dominic. PS I can send the full errors if that would be helpful. >>>

Re: [Numpy-discussion] numpy.test() failure

On Wed, Sep 14, 2011 at 2:45 PM, Samuel John wrote: > Hi Nils, > > which version of numpy, which os? > I can infer that you use python 2.6 in 64bit, right? > > Right after the beginning of the numpy.test() are some crucial information. > > bests > Samuel > > On 14.09.2011, at 22:09, Nils Wagner

Re: [Numpy-discussion] numpy.test() failure

On Wed, Sep 14, 2011 at 10:45 PM, Samuel John wrote: > Hi Nils, > > which version of numpy, which os? > Latest master. Due to https://github.com/numpy/numpy/commit/af22fc43 Travis, did you run the test suite? arange is used but not imported. Ralf > I can infer that you use python 2.6 in 64b

Re: [Numpy-discussion] numpy.test() failure

Hi Nils, which version of numpy, which os? I can infer that you use python 2.6 in 64bit, right? Right after the beginning of the numpy.test() are some crucial information. bests Samuel On 14.09.2011, at 22:09, Nils Wagner wrote: > ERROR: test_polyfit (test_polynomial.TestDocs) > -

[Numpy-discussion] numpy.test() failure

ERROR: test_polyfit (test_polynomial.TestDocs) -- Traceback (most recent call last): File "/home/nwagner/local/lib64/python2.6/site-packages/numpy/lib/tests/test_polynomial.py", line 106, in test_polyfit weights = arange

Re: [Numpy-discussion] numpy.test() Program received signal SIGABRT, Aborted.

On Fri, Dec 3, 2010 at 12:56 AM, Nils Wagner wrote: > On Fri, 03 Dec 2010 08:47:32 +0100 > "Nils Wagner" wrote: > > On Fri, 3 Dec 2010 00:42:16 -0700 > > Charles R Harris wrote: > >> On Fri, Dec 3, 2010 at 12:29 AM, Nils Wagner > >> wrote: > >> > >>> Hi all, > >>> > >>> I have installed the l

Re: [Numpy-discussion] numpy.test() Program received signal SIGABRT, Aborted.

On Fri, 03 Dec 2010 08:47:32 +0100 "Nils Wagner" wrote: > On Fri, 3 Dec 2010 00:42:16 -0700 > Charles R Harris wrote: >> On Fri, Dec 3, 2010 at 12:29 AM, Nils Wagner >> wrote: >> >>> Hi all, >>> >>> I have installed the latest version of numpy. >>> >>> >>> numpy.__version__ >>> '2.0.0.dev-6aa

Re: [Numpy-discussion] numpy.test() Program received signal SIGABRT, Aborted.

On Fri, 3 Dec 2010 00:42:16 -0700 Charles R Harris wrote: > On Fri, Dec 3, 2010 at 12:29 AM, Nils Wagner > wrote: > >> Hi all, >> >> I have installed the latest version of numpy. >> >> >>> numpy.__version__ >> '2.0.0.dev-6aacc2d' >> >> > > I don't see that here or on the buildbots. There was a

Re: [Numpy-discussion] numpy.test() Program received signal SIGABRT, Aborted.

On Fri, Dec 3, 2010 at 12:29 AM, Nils Wagner wrote: > Hi all, > > I have installed the latest version of numpy. > > >>> numpy.__version__ > '2.0.0.dev-6aacc2d' > > I don't see that here or on the buildbots. There was a problem with segfaults that was fixed in commit c0e1cf27b55dfd5a

[Numpy-discussion] numpy.test() Program received signal SIGABRT, Aborted.

Hi all, I have installed the latest version of numpy. >>> numpy.__version__ '2.0.0.dev-6aacc2d' numpy.test(verbose=2) received signal SIGABRT. test_cdouble_2 (test_linalg.TestEig) ... ok test_csingle (test_linalg.TestEig) ... FAIL *** glibc detected *** /data/home/nwagner/local/bin/python: fre

Re: [Numpy-discussion] numpy.test() errors

On 23 November 2010 23:44, Pauli Virtanen wrote: > On Tue, 23 Nov 2010 23:24:25 +0200, Stéfan van der Walt wrote: > There's this on Python 3.2: > > == > ERROR: test_io.test_gzip_load > -

Re: [Numpy-discussion] numpy.test() errors

On Tue, 23 Nov 2010 23:24:25 +0200, Stéfan van der Walt wrote: > 2010/11/23 Stéfan van der Walt : >> On Tue, Nov 23, 2010 at 9:28 AM, Nils Wagner >> wrote: >>> "/data/home/nwagner/local/lib/python2.5/site-packages/numpy/lib/npyio.py", >>> line 66, in seek_gzip_factory >>>     g.name = f.name >>> A

Re: [Numpy-discussion] numpy.test() errors

2010/11/23 Stéfan van der Walt : > On Tue, Nov 23, 2010 at 9:28 AM, Nils Wagner > wrote: >> "/data/home/nwagner/local/lib/python2.5/site-packages/numpy/lib/npyio.py", >> line 66, in seek_gzip_factory >>     g.name = f.name >> AttributeError: GzipFile instance has no attribute 'name' > > This one i

Re: [Numpy-discussion] numpy.test() errors

On Tue, 23 Nov 2010 16:39:13 +0100 Gerrit Holl wrote: > 2010/11/23 Stéfan van der Walt : >> On Tue, Nov 23, 2010 at 9:28 AM, Nils Wagner >> wrote: >>> "/data/home/nwagner/local/lib/python2.5/site-packages/numpy/lib/npyio.py", >>> line 66, in seek_gzip_factory >>>     g.name = f.name >>> Attribu

Re: [Numpy-discussion] numpy.test() errors

2010/11/23 Stéfan van der Walt : > On Tue, Nov 23, 2010 at 9:28 AM, Nils Wagner > wrote: >> "/data/home/nwagner/local/lib/python2.5/site-packages/numpy/lib/npyio.py", >> line 66, in seek_gzip_factory >>     g.name = f.name >> AttributeError: GzipFile instance has no attribute 'name' > > This one i

Re: [Numpy-discussion] numpy.test() errors

On Tue, Nov 23, 2010 at 9:28 AM, Nils Wagner wrote: > "/data/home/nwagner/local/lib/python2.5/site-packages/numpy/lib/npyio.py", > line 66, in seek_gzip_factory >     g.name = f.name > AttributeError: GzipFile instance has no attribute 'name' This one is mine--the change was made to avoid a depre

[Numpy-discussion] numpy.test() errors

Hi all, There are some new test errors == ERROR: Test with missing and filling values -- Traceback (most recent call last): File "/data/home/nwagner/local/li

Re: [Numpy-discussion] numpy.test() segfaults '2.0.0.dev8716'

Wed, 20 Oct 2010 19:21:15 +0200, Nils Wagner wrote: > test_duplicate_field_names_assign > (test_regression.TestRegression) ... Works for me. This is exactly the crash that the test tests, so perhaps you have an incomplete rebuild. I'd try "rm -rf build" and rebuild. -- Pauli Virtanen _

[Numpy-discussion] numpy.test() segfaults '2.0.0.dev8716'

test_duplicate_field_names_assign (test_regression.TestRegression) ... FF Program received signal SIGSEGV, Segmentation fault. 0x77b3077a in ?? () from /usr/lib64/libpython2.6.so.1.0 (gdb) bt #0 0x77b3077a in ?? () from /usr/lib64/libpython2.6.so.1.0 #1 0x0

Re: [Numpy-discussion] numpy.test() failures in 2.0.0.dev8233

On Sun, 21 Feb 2010 13:22:41 +0200 Pauli Virtanen wrote: > Hi, > > Please remind me what platform you are running on. Also, >please update > and re-run the tests, and check the output from > > import numpy as np > from numpy.core.multiarray import memorysimpleview as >memoryview > > dt = [(

Re: [Numpy-discussion] numpy.test() failures in 2.0.0.dev8233

Hi, Please remind me what platform you are running on. Also, please update and re-run the tests, and check the output from import numpy as np from numpy.core.multiarray import memorysimpleview as memoryview dt = [('a', np.int8), ('b', np.int16), ('c', np.int32), ('d', np.int64), ('e'

[Numpy-discussion] numpy.test() failures in 2.0.0.dev8233

== FAIL: test_multiarray.TestNewBufferProtocol.test_export_endian -- Traceback (most recent call last): File "/home/nwagner/local/lib64/python2.6/site-packag

Re: [Numpy-discussion] numpy.test(): invalid value encountered in {isinf, divide, power, ...}

On Jan 21, 2010, at 5:27 PM, David Cournapeau wrote: > On Fri, Jan 22, 2010 at 7:14 AM, David Cournapeau wrote: >> On Fri, Jan 22, 2010 at 12:06 AM, Charles R Harris >> wrote: >>> >>> >>> On Thu, Jan 21, 2010 at 3:03 AM, David Cournapeau >>> wrote: On Thu, Jan 21, 2010 at 6:23 PM, P

Re: [Numpy-discussion] numpy.test(): invalid value encountered in {isinf, divide, power, ...}

On Fri, Jan 22, 2010 at 7:14 AM, David Cournapeau wrote: > On Fri, Jan 22, 2010 at 12:06 AM, Charles R Harris > wrote: >> >> >> On Thu, Jan 21, 2010 at 3:03 AM, David Cournapeau >> wrote: >>> >>> On Thu, Jan 21, 2010 at 6:23 PM, Pauli Virtanen wrote: >>> > Wed, 20 Jan 2010 16:57:01 -0500, Darre

Re: [Numpy-discussion] numpy.test(): invalid value encountered in {isinf, divide, power, ...}

On Fri, Jan 22, 2010 at 12:06 AM, Charles R Harris wrote: > > > On Thu, Jan 21, 2010 at 3:03 AM, David Cournapeau > wrote: >> >> On Thu, Jan 21, 2010 at 6:23 PM, Pauli Virtanen wrote: >> > Wed, 20 Jan 2010 16:57:01 -0500, Darren Dale wrote: >> > [clip] >> >> Warning: invalid value encountered in

Re: [Numpy-discussion] numpy.test(): invalid value encountered in {isinf, divide, power, ...}

On Thu, Jan 21, 2010 at 3:03 AM, David Cournapeau wrote: > On Thu, Jan 21, 2010 at 6:23 PM, Pauli Virtanen > > > wrote: > > Wed, 20 Jan 2010 16:57:01 -0500, Darren Dale wrote: > > [clip] > >> Warning: invalid value encountered in isinf Warning: invalid value > >> encountered in isfinite > > [clip

Re: [Numpy-discussion] numpy.test(): invalid value encountered in {isinf, divide, power, ...}

Thu, 21 Jan 2010 19:03:06 +0900, David Cournapeau wrote: > On Thu, Jan 21, 2010 at 6:23 PM, Pauli Virtanen wrote: >> Wed, 20 Jan 2010 16:57:01 -0500, Darren Dale wrote: [clip] >>> Warning: invalid value encountered in isinf Warning: invalid value >>> encountered in isfinite >> [clip] >> >> This is

Re: [Numpy-discussion] numpy.test(): invalid value encountered in {isinf, divide, power, ...}

On Thu, Jan 21, 2010 at 6:23 PM, Pauli Virtanen wrote: > Wed, 20 Jan 2010 16:57:01 -0500, Darren Dale wrote: > [clip] >> Warning: invalid value encountered in isinf Warning: invalid value >> encountered in isfinite > [clip] > > This is because of changed seterr() default values. > > IMHO, the 'pri

Re: [Numpy-discussion] numpy.test(): invalid value encountered in {isinf, divide, power, ...}

Wed, 20 Jan 2010 16:57:01 -0500, Darren Dale wrote: [clip] > Warning: invalid value encountered in isinf Warning: invalid value > encountered in isfinite [clip] This is because of changed seterr() default values. IMHO, the 'print' default is slightly worse than the previous 'ignore'. Personally,

Re: [Numpy-discussion] numpy.test(): invalid value encountered in {isinf, divide, power, ...}

On Jan 20, 2010, at 4:57 PM, Darren Dale wrote: > I haven't been following development on the trunk closely, so I > apologize if this is a known issue. I didn't see anything relevant > when I searched the list. > > I just updated my checkout of the trunk, cleaned out the old > installation and bui

[Numpy-discussion] numpy.test(): invalid value encountered in {isinf, divide, power, ...}

I haven't been following development on the trunk closely, so I apologize if this is a known issue. I didn't see anything relevant when I searched the list. I just updated my checkout of the trunk, cleaned out the old installation and build/, and reinstalled. When I run the test suite (without spe

Re: [Numpy-discussion] numpy.test() failures

ma, 2009-12-07 kello 22:36 +0100, Nils Wagner kirjoitti: > >>> numpy.__version__ > '1.5.0.dev7980' > > FAIL: test_buffer_hashlib (test_regression.TestRegression) Thx, fixed. I forgot about defaulting to int64. Pauli ___ NumPy-Discussion maili

[Numpy-discussion] numpy.test() failures

>>> numpy.__version__ '1.5.0.dev7980' FAIL: test_buffer_hashlib (test_regression.TestRegression) -- Traceback (most recent call last): File "/home/nwagner/local/lib64/python2.6/site-packages/numpy/core/tests/test_regression.p

Re: [Numpy-discussion] numpy.test() errors r6862

On Sun, 12 Apr 2009 12:56:46 -0600 Charles R Harris wrote: > On Sun, Apr 12, 2009 at 12:52 PM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> >> On Sun, Apr 12, 2009 at 12:17 PM, Nils Wagner < >> nwag...@iam.uni-stuttgart.de> wrote: >> >>> ===

Re: [Numpy-discussion] numpy.test() errors r6862

Hi Nils, On Sun, Apr 12, 2009 at 12:17 PM, Nils Wagner wrote: > == > ERROR: test suite > -- > Traceback (most recent call last): > File > > "/home/nwagner/loca

Re: [Numpy-discussion] numpy.test() errors r6862

On Sun, Apr 12, 2009 at 12:52 PM, Charles R Harris < charlesr.har...@gmail.com> wrote: > > > On Sun, Apr 12, 2009 at 12:17 PM, Nils Wagner < > nwag...@iam.uni-stuttgart.de> wrote: > >> == >> ERROR: test suite >> --

Re: [Numpy-discussion] numpy.test() errors r6862

On Sun, Apr 12, 2009 at 12:17 PM, Nils Wagner wrote: > == > ERROR: test suite > -- > Traceback (most recent call last): > File > > "/home/nwagner/local/lib64/py

[Numpy-discussion] numpy.test() errors r6862

== ERROR: test suite -- Traceback (most recent call last): File "/home/nwagner/local/lib64/python2.6/site-packages/nose-0.10.4-py2.6.egg/nose/suite.py", line

[Numpy-discussion] numpy.test() failures

>>> numpy.__version__ '1.3.0.dev6283' == FAIL: Check formatting. -- Traceback (most recent call last): File "/usr/local/lib64/python2.5/site-packages/nose-0.1

Re: [Numpy-discussion] numpy.test() failures (1.2.1) on Mac OS X

On Tue, 30 Dec 2008, Nicholas Matsakis wrote: > I just installed what I believe to be a completely vanilla installation of > numpy on an Intel Mac OS X 10.5.6. Python 2.5 pkg from Python.org, numpy > 1.2.1 pkg from scipy.org, nose installed through setup tools. Running > "import numpy; numpy.te

[Numpy-discussion] numpy.test() failures (1.2.1) on Mac OS X

I just installed what I believe to be a completely vanilla installation of numpy on an Intel Mac OS X 10.5.6. Python 2.5 pkg from Python.org, numpy 1.2.1 pkg from scipy.org, nose installed through setup tools. Running "import numpy; numpy.test()" results in the following errors and failures:

Re: [Numpy-discussion] Numpy.test() hangs

> It's working on the buildbots. Did you remove the build directory first? Oops. Great, all working now! James ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Numpy.test() hangs

On Tue, Nov 11, 2008 at 4:13 PM, James Philbin <[EMAIL PROTECTED]> wrote: > > I think this is now fixed in svn, I'm trying to see if static fixes the > > problem with the old buggy version. What optimization level is numpy > being > > compiled with? > Still a problem here: > > In [1]: import numpy

Re: [Numpy-discussion] Numpy.test() hangs

> I think this is now fixed in svn, I'm trying to see if static fixes the > problem with the old buggy version. What optimization level is numpy being > compiled with? Still a problem here: In [1]: import numpy as np In [2]: np.__version__ Out[2]: '1.3.0.dev6011' In [3]: np.log1p(np.array([1],dt

Re: [Numpy-discussion] Numpy.test() hangs

On Tue, Nov 11, 2008 at 2:25 PM, Charles R Harris <[EMAIL PROTECTED] > wrote: > > > On Tue, Nov 11, 2008 at 1:16 PM, James Philbin <[EMAIL PROTECTED]> wrote: > >> Hmmm... So I examined an objdump of umath.so: >> objdump -d /usr/lib/python2.5/site-packages/numpy/core/umath.so > >> umath.asm >> >> T

Re: [Numpy-discussion] Numpy.test() hangs

On Tue, Nov 11, 2008 at 1:16 PM, James Philbin <[EMAIL PROTECTED]> wrote: > Hmmm... So I examined an objdump of umath.so: > objdump -d /usr/lib/python2.5/site-packages/numpy/core/umath.so > umath.asm > > The relevant lines are here: > --- > 000292c0 : > 292c0: e9 fb ff ff ff

Re: [Numpy-discussion] Numpy.test() hangs

Hmmm... So I examined an objdump of umath.so: objdump -d /usr/lib/python2.5/site-packages/numpy/core/umath.so > umath.asm The relevant lines are here: --- 000292c0 : 292c0: e9 fb ff ff ff jmpq 292c0 292c5: 66 66 2e 0f 1f 84 00nopw %cs:0x0(%rax,%rax,1)

Re: [Numpy-discussion] Numpy.test() hangs

> My guess is that this is a libm/gcc problem on x86_64, perhaps depending on > the flags libm was compiled with. What distro are you using? Ubuntu 8.10 amd64 > Can you try plain old log/log10 also? I'll try to put together some c code > you can use to check things also so that you can file a bug

Re: [Numpy-discussion] Numpy.test() hangs

On Tue, Nov 11, 2008 at 12:41 PM, James Philbin <[EMAIL PROTECTED]> wrote: > > Can you try checking the functions log1p and exp separately for all three > > floating types? Something like > > Well, log1p seems to be the culprit: > > >>> import numpy as np > >>> np.log1p(np.ones(1,dtype='f')*3) > .

Re: [Numpy-discussion] Numpy.test() hangs

> Can you try checking the functions log1p and exp separately for all three > floating types? Something like Well, log1p seems to be the culprit: >>> import numpy as np >>> np.log1p(np.ones(1,dtype='f')*3) ... hangs here ... exp is fine: >>> import numpy as np >>> np.exp(np.ones(1,dtype='f')*3)

Re: [Numpy-discussion] Numpy.test() hangs

On Tue, Nov 11, 2008 at 11:13 AM, Charles R Harris < [EMAIL PROTECTED]> wrote: > > > On Tue, Nov 11, 2008 at 11:00 AM, Charles R Harris < > [EMAIL PROTECTED]> wrote: > >> >> >> On Tue, Nov 11, 2008 at 10:33 AM, James Philbin <[EMAIL PROTECTED]>wrote: >> >>> Python 2.5.2 (r252:60911, Oct 5 2008, 1

Re: [Numpy-discussion] Numpy.test() hangs

On Tue, Nov 11, 2008 at 11:00 AM, Charles R Harris < [EMAIL PROTECTED]> wrote: > > > On Tue, Nov 11, 2008 at 10:33 AM, James Philbin <[EMAIL PROTECTED]>wrote: > >> Python 2.5.2 (r252:60911, Oct 5 2008, 19:29:17) >> [GCC 4.3.2] on linux2 >> Type "help", "copyright", "credits" or "license" for more

Re: [Numpy-discussion] Numpy.test() hangs

On Tue, Nov 11, 2008 at 10:33 AM, James Philbin <[EMAIL PROTECTED]> wrote: > Python 2.5.2 (r252:60911, Oct 5 2008, 19:29:17) > [GCC 4.3.2] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>> import numpy > >>> numpy.__version__ > '1.3.0.dev6005' > >>> numpy.te

[Numpy-discussion] Numpy.test() hangs

Python 2.5.2 (r252:60911, Oct 5 2008, 19:29:17) [GCC 4.3.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import numpy >>> numpy.__version__ '1.3.0.dev6005' >>> numpy.test(verbosity=2) ... test_umath.TestLogAddExp.test_logaddexp_values ... The test hangs at

Re: [Numpy-discussion] numpy.test error: test_hdquantiles

On Sun, May 25, 2008 at 3:35 PM, Joshua Lippai <[EMAIL PROTECTED]> wrote: > I seem to be getting a few errors and failures with the current numpy > SVN (1.2.0.dev5236). I get this output with numpy.test(1,10): > > ERROR: Ticket #396 > ---

[Numpy-discussion] numpy.test error: test_hdquantiles

I seem to be getting a few errors and failures with the current numpy SVN (1.2.0.dev5236). I get this output with numpy.test(1,10): ERROR: Ticket #396 -- Traceback (most recent call last): File "/Library/Frameworks/Python.frame

Re: [Numpy-discussion] numpy.test() (failures=2, errors=3)

On Sat, 24 May 2008 08:49:12 -0600 "Charles R Harris" <[EMAIL PROTECTED]> wrote: > On Sat, May 24, 2008 at 6:54 AM, Nils Wagner ><[EMAIL PROTECTED]> > wrote: > >> Hi all, >> >> I found two failures and three errors wrt numpy.test() >> >> numpy.__version__ >> >> '1.2.0.dev5228' >> >

Re: [Numpy-discussion] numpy.test() (failures=2, errors=3)

On Sat, May 24, 2008 at 6:54 AM, Nils Wagner <[EMAIL PROTECTED]> wrote: > Hi all, > > I found two failures and three errors wrt numpy.test() > > numpy.__version__ > > '1.2.0.dev5228' > Hi Nils, can you try a clean install? Remove the build directory and maybe the numpy folder in site

Re: [Numpy-discussion] numpy.test() (failures=2, errors=3)

> == > ERROR: test_hdquantiles > (numpy.ma.tests.test_morestats.TestQuantiles) > -- You have some kind of franken-build going on there. test_morestats has long s

[Numpy-discussion] numpy.test() (failures=2, errors=3)

Hi all, I found two failures and three errors wrt numpy.test() numpy.__version__ '1.2.0.dev5228' == ERROR: Ticket #396 -- Traceback (most recent c

Re: [Numpy-discussion] numpy.test() fails if it runs after scipy.test()

That's very strange, I've made a local installation of numpy 1.0.4 and scipy 0.6 from official source, and I use the same kind of installation script as in http://www.scipy.org/Installing_SciPy/Linux/BuildingFromSource/GCC_1, so I always erase all the local directory to prevent this kind of confl

Re: [Numpy-discussion] numpy.test() fails if it runs after scipy.test()

Loic, I was not able to reproduce this. Have you tried doing a clean install by removing your numpy and scipy directories in the site-packages and reinstalling. I've had old files in my install directory cause problems in the past. You are correct, the tests should not effect one another. Chri

[Numpy-discussion] numpy.test() fails if it runs after scipy.test()

Hi, I've got one failure if I run numpy.test() after running scipy.test() : == ERROR: Ticket #396 -- Traceback (most recent call last): File "/home/loic/tmp/

Re: [Numpy-discussion] numpy.test error on G5 PPC

Vincent Nijs wrote: > == > FAIL: check_large_types (numpy.core.tests.test_scalarmath.test_power) > -- > Traceback (most recent call last): > File > "/Library/Fr

[Numpy-discussion] numpy.test error on G5 PPC

Mac OS X 10.4.8 G5 PPC Numpy svn: 2602 Target: powerpc-apple-darwin8 Configured with: /private/var/tmp/gcc/gcc-5367.obj~1/src/configure --disable-checking -enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/$/-4.0/ --with

[Numpy-discussion] numpy.test

I'd like to add numpy.test(level=10, verbosity=0) to the top of my program. Is there a way for my program to find out if all tests passed? Or even better, how many tests ran and how many of those failed. Is there any way to suppress all output of numpy.test? verbosity=0 stops most, but not all, o