On Mon, Mar 30, 2009 at 3:04 PM, Mark Sienkiewicz <sienk...@stsci.edu>wrote:
>
> >> ======================================================================
> >> FAIL: Test find_duplicates
> >> ----------------------------------------------------------------------
> >> ...
> >> AssertionError:
> >> Arrays are not equal
> >>
> >> (mismatch 50.0%)
> >> x: array([(1, (2.0, 'B')), (2, (2.0, 'B')), (2, (2.0, 'B')), (1, (2.0,
> >> 'B'))],
> >> dtype=[('A', '>i4'), ('B', [('BA', '>f8'), ('BB', '|S1')])])
> >> y: array([(2, (2.0, 'B')), (1, (2.0, 'B')), (2, (2.0, 'B')), (1, (2.0,
> >> 'B'))],
> >> dtype=[('A', '>i4'), ('B', [('BA', '>f8'), ('BB', '|S1')])])
> >>
> >> ----------------------------------------------------------------------
> >>
> >>
> >
> > These are new (two months old) tests. Hmm, they are also marked as known
> > failures on win32. I wonder why they fail there and not on linux? I think
> > you should open a ticket for this.
> >
>
> I'm not sure how old the test is, but I see that it has been failing
> since Feb 1. (That is the earliest report I have online at the moment.)
>
> The ticket is http://projects.scipy.org/numpy/ticket/1039 . I added
> this specific failure mode to the ticket today.
>
> It does not surprise me at all when the trunk is broken on solaris. I'm
> mentioning it on the list because I see it is still broken in the
> release candidate. I assume somebody would want to either fix the
> problem or remove the non-working feature from the release.
>
I'm guessing that it is the test that needs fixing. And maybe the windows
problem is related.
Chuck
_______________________________________________
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
