Hi all,
here's the output difference between 32/64 bit tests run: bic128[scipy]$ diff -u tests_32.txt tests_64.txt --- tests_32.txt 2008-04-07 15:54:29.000000000 -0700 +++ tests_64.txt 2008-04-07 15:53:58.000000000 -0700 @@ -611,12 +611,6 @@ testip_types (numpy.core.tests.test_multiarray.TestPutmask) ... ok testip_types (numpy.core.tests.test_multiarray.TestPutmask) ... ok testip_types (numpy.core.tests.test_multiarray.TestPutmask) ... ok -testip_types (numpy.core.tests.test_multiarray.TestPutmask) ... ok -testip_types (numpy.core.tests.test_multiarray.TestPutmask) ... ok -testip_types (numpy.core.tests.test_multiarray.TestPutmask) ... ok -testip_types (numpy.core.tests.test_multiarray.TestPutmask) ... ok -testip_types (numpy.core.tests.test_multiarray.TestPutmask) ... ok -testip_types (numpy.core.tests.test_multiarray.TestPutmask) ... ok testip_zero (numpy.tests.test_linalg.TestMatrixPower) ... ok testip_zero (numpy.tests.test_linalg.TestMatrixPower) ... ok testip_zero (numpy.tests.test_linalg.TestMatrixPower) ... ok On 32 bits, 869 are found and on Fedora x86_64, it's 863. Above is the difference (requested by rkern). Gotta run... f _______________________________________________ Numpy-discussion mailing list [hidden email] http://projects.scipy.org/mailman/listinfo/numpy-discussion |
On Mon, Apr 7, 2008 at 3:56 PM, Fernando Perez <[hidden email]> wrote:
> Hi all, > > here's the output difference between 32/64 bit tests run: > > bic128[scipy]$ diff -u tests_32.txt tests_64.txt > --- tests_32.txt 2008-04-07 15:54:29.000000000 -0700 > +++ tests_64.txt 2008-04-07 15:53:58.000000000 -0700 > @@ -611,12 +611,6 @@ > testip_types (numpy.core.tests.test_multiarray.TestPutmask) ... ok > testip_types (numpy.core.tests.test_multiarray.TestPutmask) ... ok > testip_types (numpy.core.tests.test_multiarray.TestPutmask) ... ok > -testip_types (numpy.core.tests.test_multiarray.TestPutmask) ... ok > -testip_types (numpy.core.tests.test_multiarray.TestPutmask) ... ok > -testip_types (numpy.core.tests.test_multiarray.TestPutmask) ... ok > -testip_types (numpy.core.tests.test_multiarray.TestPutmask) ... ok > -testip_types (numpy.core.tests.test_multiarray.TestPutmask) ... ok > -testip_types (numpy.core.tests.test_multiarray.TestPutmask) ... ok > testip_zero (numpy.tests.test_linalg.TestMatrixPower) ... ok > testip_zero (numpy.tests.test_linalg.TestMatrixPower) ... ok > testip_zero (numpy.tests.test_linalg.TestMatrixPower) ... ok > > > On 32 bits, 869 are found and on Fedora x86_64, it's 863. Above is > the difference (requested by rkern). I think this is fine. The different arises because of extra scalar types on the 32 bit system that don't show up on the AMD system, presumably float96 and complex192. Check numpy.sctypes for the difference. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco _______________________________________________ Numpy-discussion mailing list [hidden email] http://projects.scipy.org/mailman/listinfo/numpy-discussion |
On Mon, Apr 7, 2008 at 4:04 PM, Robert Kern <[hidden email]> wrote:
> > On 32 bits, 869 are found and on Fedora x86_64, it's 863. Above is > > the difference (requested by rkern). > > I think this is fine. The different arises because of extra scalar > types on the 32 bit system that don't show up on the AMD system, > presumably float96 and complex192. Check numpy.sctypes for the > difference. - complex192 isn't on the 64bit box, but complex256 is, so that keeps the number of tests for that type equal. - float96 -> float128, again no change in test count - for some reason, the 32-bit box gives 'int': [<type 'numpy.int8'>, <type 'numpy.int16'>, <type 'numpy.int32'>, <type 'numpy.int32'>, <type 'numpy.int64'>], so there's a repeated int32 type listed there. I don't know what that means, but obviously it produces extra tests (possibly redundant?) - Same for uint: 'uint': [<type 'numpy.uint8'>, <type 'numpy.uint16'>, <type 'numpy.uint32'>, <type 'numpy.uint32'>, <type 'numpy.uint64'>]} In any case, other than this minor difference, current numpy SVN passes all tests on Fedora8/64bit and Ubuntu Gutsy/32bit. Cheers, f _______________________________________________ Numpy-discussion mailing list [hidden email] http://projects.scipy.org/mailman/listinfo/numpy-discussion |
On Mon, Apr 7, 2008 at 6:29 PM, Fernando Perez <[hidden email]> wrote:
> On Mon, Apr 7, 2008 at 4:04 PM, Robert Kern <[hidden email]> wrote: > > > > On 32 bits, 869 are found and on Fedora x86_64, it's 863. Above is > > > the difference (requested by rkern). > > > > I think this is fine. The different arises because of extra scalar > > types on the 32 bit system that don't show up on the AMD system, > > presumably float96 and complex192. Check numpy.sctypes for the > > difference. > > - complex192 isn't on the 64bit box, but complex256 is, so that keeps > the number of tests for that type equal. > > - float96 -> float128, again no change in test count > > - for some reason, the 32-bit box gives > 'int': [<type 'numpy.int8'>, > <type 'numpy.int16'>, > <type 'numpy.int32'>, > <type 'numpy.int32'>, > <type 'numpy.int64'>], > > so there's a repeated int32 type listed there. I don't know what that > means, but obviously it produces extra tests (possibly redundant?) Definitely redundant, but harmless. The code that generates these lists is numpy/core/numerictypes.py:_set_array_types(). The redundant ones are dtype('p').type and dtype('P').type. For some reason these do not compare equal to numpy.{u}int32. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco _______________________________________________ Numpy-discussion mailing list [hidden email] http://projects.scipy.org/mailman/listinfo/numpy-discussion |
Free forum by Nabble | Edit this page |