Mysterious test_pareto failure on Travis #424
Milestone
Comments
This was referenced Sep 4, 2012
certik
added a commit
to certik/numpy
that referenced
this issue
Sep 4, 2012
Fixes numpy#424 The problem was that in 32bit Ubuntu 12.04, one gets the following: > /home/njs/numpy/.tox/py27/local/lib/python2.7/site-packages/numpy/random/tests/test_random.py(363)test_pareto() -> np.testing.assert_array_almost_equal(actual, desired, decimal=15) (Pdb) actual[1, 0] 52828779.702948704 (Pdb) desired[1, 0] 52828779.702948518 and the test was comparing the numbers to 1e-14, which obviously failed. Now we compare them to 1e-6, which works.
certik
pushed a commit
to certik/numpy
that referenced
this issue
Sep 13, 2012
The problem was that in 32bit Ubuntu 12.04, one gets the following: > /home/njs/numpy/.tox/py27/local/lib/python2.7/site-packages/numpy/random/tests/test_random.py(363)test_pareto() -> np.testing.assert_array_almost_equal(actual, desired, decimal=15) (Pdb) actual[1, 0] 52828779.702948704 (Pdb) desired[1, 0] 52828779.702948518 and the test was comparing the numbers to 1e-14, which obviously failed. Fixes numpy#424.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See here for a discussion:
http://mail.scipy.org/pipermail/numpy-discussion/2012-September/063801.html
The failure is caused by Travis switching to 32bit Ubuntu 12.04 recently. Some change in Ubuntu breaks it. Even this old commit 3882d65 still has the failure, so it's probably gcc related. The test is probably not robust enough.
The text was updated successfully, but these errors were encountered: