[SPARK-54937][PYTHON][TESTS] Add tests for timezone conversion w/o PYARROW_IGNORE_TIMEZONE #53712
+221
−0
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
JIRA Issue Information=== Sub-task SPARK-54937 === This comment was automatically generated by GitHub Actions |
zhengruifeng
force-pushed
the
test_ingore_timezone
branch
from
8b2b64a to
5cc3c96
Compare
zhengruifeng
force-pushed
the
test_ingore_timezone
branch
from
5cc3c96 to
f2b7e48
Compare
HyukjinKwon
approved these changes
Jan 7, 2026
Member
|
Merged to master. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What changes were proposed in this pull request?
Add tests for timezone conversion w/o PYARROW_IGNORE_TIMEZONE
Why are the changes needed?
The test is pretty fast (<0.1s), we want to use such test to monitor behavior changes from upstream projects.
We will be aware of breaking changes of important functions in the future.
Does this PR introduce any user-facing change?
No, test-only
How was this patch tested?
CI
Was this patch authored or co-authored using generative AI tooling?
No