-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
TST: stricter xfails, catch/suppress warnings #33882
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
Conversation
* remove \n from docstring * fix issue 17038 * revert change * revert change * Remove TODO
on a travis build |
result = op(array, nulls_fixture) | ||
expected = self.elementwise_comparison(op, array, nulls_fixture) | ||
|
||
if nulls_fixture is pd.NA and array.dtype != pd.IntervalDtype("int"): | ||
pytest.xfail("broken for non-integer IntervalArray; see GH 31882") | ||
mark = pytest.mark.xfail( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps a helpful function for this if we are going to do across the codebase? Jeff's idea - here
I'm happy to tackle some myself too :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Go for it. I think this is a strictly better pattern than pytest.xfail
, since it will alert us if an xfail becomes fixed.
thanks |
Remove box_df_fail which is no longer used