Pauli Virtanen wrote:
>
> Probably they are both related to unspecified sort order for
> the duplicates. There were some sort-order ignoring missing in the test.
>
> I think the test is now fixed in trunk:
>
> http://projects.scipy.org/numpy/changeset/6827
>
The test passes in 1.4.0.dev68
Mon, 30 Mar 2009 15:15:06 -0600, Charles R Harris wrote:
> I'm guessing that it is the test that needs fixing. And maybe the windows
> problem is related.
Probably they are both related to unspecified sort order for
the duplicates. There were some sort-order ignoring missing in the test.
I think
On Mon, Mar 30, 2009 at 3:04 PM, Mark Sienkiewicz wrote:
>
> >> ==
> >> FAIL: Test find_duplicates
> >> --
> >> ...
> >> AssertionError:
> >> Arrays are not equal
Mon, 30 Mar 2009 14:03:17 -0600, Charles R Harris wrote:
> On Mon, Mar 30, 2009 at 10:28 AM, Mark Sienkiewicz
> wrote:
>
>> Numpy 1.3.0 rc1 fails this self-test on Solaris.
[clip]
>> ==
>> FAIL: Test find_duplicates
>> --
>> ==
>> FAIL: Test find_duplicates
>> --
>> ...
>> AssertionError:
>> Arrays are not equal
>>
>> (mismatch 50.0%)
>> x: array([(1, (2.0, 'B')), (2, (2.0, 'B')),
On Mon, Mar 30, 2009 at 10:28 AM, Mark Sienkiewicz wrote:
> Numpy 1.3.0 rc1 fails this self-test on Solaris.
>
>
> ==
> FAIL: Test find_duplicates
> --
> Tracebac
Numpy 1.3.0 rc1 fails this self-test on Solaris.
==
FAIL: Test find_duplicates
--
Traceback (most recent call last):
File "/usr/ra/pyssg/2.5.1/numpy/lib/tests/
