-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
TST/CI: xfail test_round_sanity for 32 bit #47803
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
@@ -297,6 +298,7 @@ def test_round_implementation_bounds(self): | |||
with pytest.raises(OverflowError, match=msg): | |||
Timestamp.max.ceil("s") | |||
|
|||
@pytest.mark.xfail(not IS64, reason="Failing on 32 bit build", strict=False) |
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.
instead what if we just adjust the bounds by 1e9?
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.
So just to confirm
@given(val=st.integers(iNaT + 1 + 1e9, lib.i8max - 1e9))
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.
i guess technically should use 10**9
but yah
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.
I had to cap the max and min values to np.iinfo(np.in32)
for the 32 bit build instead
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.
that seems like something really is wrong on the 32bit build, so maybe an xfail is appropriate after all?
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.
Okay. I will change it back to xfail(strict=False)
because I think the hypothesis still doesn't fail this consistently with certain params.
b57d287
to
01d72bf
Compare
Going to merge this to get the CI back to green. Will open an issue to investigate this issue. |
This comment was marked as resolved.
This comment was marked as resolved.
xref #47823 |
xfailing just to get the CI to green. Might be addressable in the future cc @jbrockmendel