TST: Fix CI failures (don't xfail postgresql / don't xfail for pyarrow=16) #58693
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…st_multi_thread_string_io_read_csv
Aloqeely
changed the title
Aloqeely
changed the title
mroeschke
reviewed
May 13, 2024
mroeschke
added
the
Testing
Co-authored-by: Matthew Roeschke <[email protected]>
|
pre-commit.ci autofix |
for more information, see https://pre-commit.ci
|
|
mroeschke
approved these changes
May 13, 2024
|
Thanks @Aloqeely |
meeseeksmachine
pushed a commit
to meeseeksmachine/pandas
that referenced
this pull request
May 13, 2024
…resql / don't xfail for pyarrow=16)
mroeschke
pushed a commit
that referenced
this pull request
May 13, 2024
… postgresql / don't xfail for pyarrow=16)) (#58709) Backport PR #58693: TST: Fix CI failures (don't xfail postgresql / don't xfail for pyarrow=16) Co-authored-by: Abdulaziz Aloqeely <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using
tm.assert_produces_warningfor the first test gives:It seems the stacklevel is set incorrectly and should be changed (see #55591), I just temporarily fixed it by using
pytest.mark.filterwarnings