[SPARK-59549][PYTHON][TEST][FOLLOWUP] Add ARM expected results for pandas.Series.astype tests - #58952
Open
Spenserrrr wants to merge 1 commit into
Open
Spenserrrr wants to merge 1 commit into
Spenserrrr wants to merge 1 commit into
Conversation
…ndas.Series.astype tests
Spenserrrr
marked this pull request as ready for review
September 21, 2026 23:24
Contributor
Author
|
Hi @gaogaotiantian @Yicong-Huang! The schedule ARM and macOS jobs failed because the new Series.astype test has different results for nonfinite float-to-temporal casts. This PR adds an override to those cells. Could you take a look when you have time? Thanks! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 ARM-specific expected results for nonfinite float-to-timestamp and float-to-timedelta casts in the upstream
Series.astypetests.Why are the changes needed?
The scheduled Linux ARM and macOS jobs convert positive infinity to the maximum int64 temporal value, while the x86 goldens record
NaT, causing both call-mode tests to fail.Does this PR introduce any user-facing change?
No.
How was this patch tested?
The upstream suite passes locally, and the affected
pyspark-coreshard passes on native Linux ARM and macOS runners with the new overrides.Was this patch authored or co-authored using generative AI tooling?
Generated-by: GPT-5