[Numpy-discussion] Failure in test_iterator.py at Travis

[Ondřej Čertík]

On Thu, Dec 13, 2012 at 7:16 PM, Charles R Harris
<charlesr.harris at gmail.com> wrote:
>
>
> On Thu, Dec 13, 2012 at 8:04 PM, Charles R Harris
> <charlesr.harris at gmail.com> wrote:
>>
>>
>>
>> On Thu, Dec 13, 2012 at 7:23 PM, Ondřej Čertík <ondrej.certik at gmail.com>
>> wrote:
>>>
>>> Hi,
>>>
>>> Another weird bug sometimes happen in
>>> numpy/core/tests/test_iterator.py, it looks like this:
>>>
>>> ======================================================================
>>> FAIL: test_iterator.test_iter_array_cast
>>> ----------------------------------------------------------------------
>>> Traceback (most recent call last):
>>>   File
>>> "/home/travis/virtualenv/python2.5/lib/python2.5/site-packages/nose/case.py",
>>> line 197, in runTest
>>>     self.test(*self.arg)
>>>   File
>>> "/home/travis/virtualenv/python2.5/lib/python2.5/site-packages/numpy/core/tests/test_iterator.py",
>>> line 836, in test_iter_array_cast
>>>     assert_equal(i.operands[0].strides, (-96,8,-32))
>>>   File
>>> "/home/travis/virtualenv/python2.5/lib/python2.5/site-packages/numpy/testing/utils.py",
>>> line 252, in assert_equal
>>>     assert_equal(actual[k], desired[k], 'item=%r\n%s' % (k,err_msg),
>>> verbose)
>>>   File
>>> "/home/travis/virtualenv/python2.5/lib/python2.5/site-packages/numpy/testing/utils.py",
>>> line 314, in assert_equal
>>>     raise AssertionError(msg)
>>> AssertionError:
>>> Items are not equal:
>>> item=0
>>>
>>>  ACTUAL: 96
>>>  DESIRED: -96
>>>
>>> ----------------------------------------------------------------------
>>>
>>>
>>> But the problem is that there is no numpy/core/tests/test_iterator.py
>>> file in current branches.... This error was triggered for example by
>>> these PRs:
>>>
>>> https://github.com/numpy/numpy/pull/2765
>>> https://github.com/numpy/numpy/pull/2815
>>>
>>> and here are links to the failing Travis tests:
>>>
>>> https://travis-ci.org/certik/numpy/builds/3656959
>>> https://travis-ci.org/numpy/numpy/builds/3330234
>>>
>>>
>>> Any idea what is happening here and how to fix it?
>>>
>>
>> That should have been fixed by Nathaniel's travis fix. Hmm...
>>
>
> And a quick check here shows pip not removing a previous 1.6.2 install.
> Maybe it is a pip version problem, pip 1.0.2 here.

That's what I thought as well. I think we need to update the Travis
script to manually remove the installed numpy.

Btw, Travis seems to be using pip 1.2.1, at least according to:

https://travis-ci.org/numpy/numpy/jobs/3330236

Ondrej