-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
TST: handle inconsistent ordering in resample_api compat test #27196
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
should fix the 3.5 occasionally failing tests |
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.
LGTM. Are we having pytest 5 issues? I can take a look.
@@ -247,7 +247,7 @@ def test_agg_consistency(): | |||
check_stacklevel=False): | |||
expected = r[['A', 'B', 'C']].agg({'r1': 'mean', 'r2': 'sum'}) | |||
result = r.agg({'r1': 'mean', 'r2': 'sum'}) | |||
assert_frame_equal(result, expected) | |||
assert_frame_equal(result, expected, check_like=True) |
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.
LGTM. This could maybe be check_like=not compat.PY36
so that we continue to check it for 3.6 and above. But I suspect we have other tests ensuring the order.
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.
yeah just saw a bunch of failures here.
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.
Yeah, I think ideally we should only do this for py 3.5
yep, I pinned < 5.0 on the 3.6 builds (already pinned on 3.5); so I think this is ok. will merge and rebase other that looks ready. |
No description provided.