Skip to content

Test failure: test_none_comparison #10835

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

Closed
cel4 opened this issue Aug 17, 2015 · 5 comments
Closed

Test failure: test_none_comparison #10835

cel4 opened this issue Aug 17, 2015 · 5 comments
Labels
Unreliable Test Unit tests that occasionally fail
Milestone

Comments

@cel4
Copy link
Contributor

cel4 commented Aug 17, 2015

test_none_comparison fails for me for all versions of numpy>=1.9.0. I don't see this issue in any numpy-1.8.x version.

ERROR: test_none_comparison (pandas.tests.test_base.TestIndexOps)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/ch/repo/pandas/.tox/py34/lib/python3.4/site-packages/pandas/tests/test_base.py", line 303, in test_none_comparison
    result = None != o
  File "/Users/ch/repo/pandas/.tox/py34/lib/python3.4/site-packages/pandas/core/generic.py", line 723, in __nonzero__
    .format(self.__class__.__name__))
ValueError: The truth value of a Series is ambiguous. Use a.empty, a.bool(), a.item(), a.any() or a.all().
@jreback
Copy link
Contributor

jreback commented Aug 18, 2015

pls supply system details. I have seen this fail, but cannot repro.

@cel4
Copy link
Contributor Author

cel4 commented Aug 18, 2015

INSTALLED VERSIONS
------------------
commit: None
python: 3.4.2.final.0
python-bits: 64
OS: Darwin
OS-release: 14.5.0
machine: x86_64
processor: i386
byteorder: little
LC_ALL: de_DE.UTF-8
LANG: de_DE.UTF-8

pandas: 0.16.2+340.ge4368de.dirty
nose: 1.3.7
Cython: 0.23
numpy: 1.9.2
scipy: None
statsmodels: None
IPython: None
sphinx: None
patsy: None
dateutil: 2.4.2
pytz: 2015.4
bottleneck: None
tables: None
numexpr: None
matplotlib: None
openpyxl: 1.8.6
xlrd: 0.9.4
xlwt: None
xlsxwriter: 0.7.3
lxml: 3.4.4
bs4: 4.4.0
html5lib: 0.999999
httplib2: None
apiclient: None
sqlalchemy: 1.0.8
pymysql: None
psycopg2: None

@kawochen
Copy link
Contributor

Can you show your tox.ini?

@cel4
Copy link
Contributor Author

cel4 commented Aug 21, 2015

# Tox (http://tox.testrun.org/) is a tool for running tests
# in multiple virtualenvs. This configuration file will run the
# test suite on all supported python versions. To use it, "pip install tox"
# and then run "tox" from this directory.

[tox]
envlist = py26, py27, py33, py34
#envlist = py27, py33, py34


[testenv]
deps =
    numpy
#    numpy==1.8.2
    cython
    nose
    pytz>=2011k
    python-dateutil
    beautifulsoup4
    lxml
    openpyxl<2.0.0
    xlsxwriter
    xlrd
    six
    sqlalchemy
    html5lib

# cd to anything but the default {toxinidir} which
# contains the pandas subdirectory and confuses
# nose away from the fresh install in site-packages
changedir = {envdir}

commands =
    # TODO:  --exe because of GH #761
    {envbindir}/nosetests --exe pandas {posargs:-A "not network and not disabled"}
    # cleanup the temp. build dir created by the tox build
#    /bin/rm -rf {toxinidir}/build

    # quietly rollback the install.
    # Note this line will only be reached if the
    # previous lines succeed (in particular, the tests),
    # but an uninstall is really only required when
    # files are removed from the source tree, in which case,
    # stale versions of files will will remain in the venv
    # until the next time uninstall is run.
    #
    # tox should provide a preinstall-commands hook.
    pip uninstall pandas -qy

[testenv:py26]
deps =
    boto
    bigquery
    {[testenv]deps}

[testenv:py27]
deps =
    boto
    bigquery
    {[testenv]deps}

[testenv:py33]
deps =
    {[testenv]deps}

[testenv:py34]
deps =
    {[testenv]deps}

@jreback jreback added the Unreliable Test Unit tests that occasionally fail label Aug 22, 2015
@jreback jreback added this to the 0.17.0 milestone Aug 22, 2015
@jreback
Copy link
Contributor

jreback commented Aug 22, 2015

This was failing sometimes on windows. 3bf4dc6

not really sure why, feel free to investigate

@jreback jreback closed this as completed Aug 22, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Unreliable Test Unit tests that occasionally fail
Projects
None yet
Development

No branches or pull requests

3 participants