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

CI: Failing np.bool on numpy master #34848

Closed
TomAugspurger opened this issue Jun 17, 2020 · 1 comment · Fixed by #34835
Closed

CI: Failing np.bool on numpy master #34848

TomAugspurger opened this issue Jun 17, 2020 · 1 comment · Fixed by #34835
Labels
CI Continuous Integration Dependencies Required and optional dependencies
Milestone

Comments

@TomAugspurger
Copy link
Contributor

=================================== FAILURES ===================================

_________________________ test_dataframe_div_silenced __________________________

[gw0] linux -- Python 3.9.0 /home/travis/virtualenv/python3.9-dev/bin/python

    def test_dataframe_div_silenced():

        # GH#26793

        pdf1 = pd.DataFrame(

            {

                "A": np.arange(10),

                "B": [np.nan, 1, 2, 3, 4] * 2,

                "C": [np.nan] * 10,

                "D": np.arange(10),

            },

            index=list("abcdefghij"),

            columns=list("ABCD"),

        )

        pdf2 = pd.DataFrame(

            np.random.randn(10, 4), index=list("abcdefghjk"), columns=list("ABCX")

        )

        with tm.assert_produces_warning(None):

>           pdf1.div(pdf2, fill_value=0)

pandas/tests/arithmetic/test_numeric.py:1311: 

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = <contextlib._GeneratorContextManager object at 0x7f00d965da90>

type = None, value = None, traceback = None

    def __exit__(self, type, value, traceback):

        if type is None:

            try:

>               next(self.gen)

E               AssertionError: Caused unexpected warning(s): [('DeprecationWarning', DeprecationWarning('`np.bool` is a deprecated alias for the builtin `bool`. Use `bool` by itself, which is identical in behavior, to silence this warning. If you specifically wanted the numpy scalar type, use `np.bool_` here.'), '/home/travis/build/pandas-dev/pandas/pandas/core/indexes/base.py', 377), ('DeprecationWarning', DeprecationWarning('`np.bool` is a deprecated alias for the builtin `bool`. Use `bool` by itself, which is identical in behavior, to silence this warning. If you specifically wanted the numpy scalar type, use `np.bool_` here.'), '/home/travis/build/pandas-dev/pandas/pandas/core/indexes/base.py', 377), ('DeprecationWarning', DeprecationWarning('`np.bool` is a deprecated alias for the builtin `bool`. Use `bool` by itself, which is identical in behavior, to silence this warning. If you specifically wanted the numpy scalar type, use `np.bool_` here.'), '/home/travis/build/pandas-dev/pandas/pandas/core/indexes/base.py', 377), ('DeprecationWarning', DeprecationWarning('`np.bool` is a deprecated alias for the builtin `bool`. Use `bool` by itself, which is identical in behavior, to silence this warning. If you specifically wanted the numpy scalar type, use `np.bool_` here.'), '/home/travis/build/pandas-dev/pandas/pandas/core/indexes/base.py', 377)]

https://travis-ci.org/github/pandas-dev/pandas/jobs/699262221

@TomAugspurger TomAugspurger added Bug Needs Triage Issue that has not been reviewed by a pandas team member CI Continuous Integration Dependencies Required and optional dependencies and removed Bug Needs Triage Issue that has not been reviewed by a pandas team member labels Jun 17, 2020
@jorisvandenbossche
Copy link
Member

I think @WillAyd is already handling that in #34835

@jreback jreback added this to the 1.1 milestone Jun 17, 2020
The-Compiler added a commit to The-Compiler/hypothesis that referenced this issue Apr 26, 2022
Mostly due to old Pandas versions:
pandas-dev/pandas#41199
pandas-dev/pandas#32056
pandas-dev/pandas#34848

In one instance, also due to Lark using sre_* modules:
lark-parser/lark#1140

Those filters could also be set to `ignore` to not show the warnings at
all. This sets them to `default`, restoring the previous behavior of
showing the warnings but not failing the test run.

Perhaps it might make sense to use older Numpy versions for testing the
older Pandas versions too?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous Integration Dependencies Required and optional dependencies
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants