Skip to content

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

Merged
merged 6 commits into from
Jul 22, 2022

Conversation

mroeschke
Copy link
Member

xfailing just to get the CI to green. Might be addressable in the future cc @jbrockmendel

@mroeschke mroeschke added CI Continuous Integration Unreliable Test Unit tests that occasionally fail labels Jul 20, 2022
@mroeschke mroeschke added this to the 1.4.4 milestone Jul 20, 2022
@@ -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)
Copy link
Member

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?

Copy link
Member Author

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))

Copy link
Member

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

Copy link
Member Author

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

Copy link
Member

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?

Copy link
Member Author

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.

@mroeschke mroeschke force-pushed the flaky/32/rounding branch from b57d287 to 01d72bf Compare July 22, 2022 16:43
@mroeschke
Copy link
Member Author

Going to merge this to get the CI back to green. Will open an issue to investigate this issue.

@mroeschke mroeschke merged commit 8c7b0b2 into pandas-dev:main Jul 22, 2022
@mroeschke mroeschke deleted the flaky/32/rounding branch July 22, 2022 19:38
@lumberbot-app

This comment was marked as resolved.

@mroeschke
Copy link
Member Author

xref #47823

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous Integration Unreliable Test Unit tests that occasionally fail
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants