Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TestAnova2.test_results fails with pandas 0.13.1 #1377

Closed
juliantaylor opened this issue Feb 8, 2014 · 2 comments

Comments

Projects
None yet
2 participants
@juliantaylor
Copy link
Contributor

commented Feb 8, 2014

with pandas 0.13.1, cython 0.20, numpy 1.7.1 and 1.8.0

it does not seem to happen with pandas 0.12, maybe they changed how NaN are handled as the element which is different originates from NaN inputs.

======================================================================
FAIL: __main__.TestAnova2.test_results
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
    self.test(*self.arg)
  File "statsmodels/stats/tests/test_anova.py", line 149, in test_results
    np.testing.assert_equal(results['df'].values, Df)
  File "/usr/lib/pymodules/python2.7/numpy/testing/utils.py", line 257, in assert_equal
    return assert_array_equal(actual, desired, err_msg, verbose)
  File "/usr/lib/pymodules/python2.7/numpy/testing/utils.py", line 719, in assert_array_equal
    verbose=verbose, header='Arrays are not equal')
  File "/usr/lib/pymodules/python2.7/numpy/testing/utils.py", line 645, in assert_array_compare
    raise AssertionError(msg)
AssertionError: 
Arrays are not equal

(mismatch 25.0%)
 x: array([ 1.,  2.,  2.,  0.])
 y: array([ 1,  2,  2, 51])

----------------------------------------------------------------------
Ran 1 test in 8.314s
@juliantaylor

This comment has been minimized.

Copy link
Contributor Author

commented Feb 8, 2014

probably a pandas bug, failures is fixed by 6d56e7300d66d3ba76684334bbb44b6cd0ea9f61 of pandas
pandas-dev/pandas#6254

@josef-pkt

This comment has been minimized.

Copy link
Member

commented Feb 8, 2014

If this is really a pandas bug, then we should have paid more attention to the pythonxy test failure.
I'm far behind in testing new versions of numpy, scipy, pandas and patsy, and most of our automatic testing also uses older versions.

Thanks Julian

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.