[Numpy-discussion] Weird Travis-CI bugs in the release 1.7.x branch

Ondřej Čertík ondrej.certik@gmail....
Mon Dec 3 20:27:42 CST 2012


Hi,

I started to work on the release again and noticed weird failures at Travis-CI:

https://github.com/numpy/numpy/pull/2782

The first commit (8a18fc7) should not trigger this failure:

======================================================================
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

So I pushed a whitespace commit into the PR (516b478) yet it has the
same failure. So it's there, it's
not some random fluke at Travis. I created this testing PR:

https://github.com/numpy/numpy/pull/2783

to try to nail it down. But I can't see what could have caused this,
because the release branch was passing all tests
last time I worked on it.

Any ideas?

Btw, I managed to reproduce the SPARC64 bug:

https://github.com/numpy/numpy/issues/2668

so that's good. Now I just need to debug it.

Ondrej

P.S. My thesis was finally approved by the grad school today,
doing some final changes took more time than expected, but
I think that I am done now.


More information about the NumPy-Discussion mailing list