[MINOR][PYTHON][TESTS] Retry test_map_in_pandas_with_column_vector#44641
Closed
zhengruifeng wants to merge 1 commit intoapache:masterfrom
Closed
[MINOR][PYTHON][TESTS] Retry test_map_in_pandas_with_column_vector#44641zhengruifeng wants to merge 1 commit intoapache:masterfrom
test_map_in_pandas_with_column_vector#44641zhengruifeng wants to merge 1 commit intoapache:masterfrom
Conversation
test_map_in_pandas_with_column_vector and its parity testtest_map_in_pandas_with_column_vector
49565eb to
4c8dcdb
Compare
HyukjinKwon
approved these changes
Jan 10, 2024
Member
|
Merged to master. |
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
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?
Retry
test_map_in_pandas_with_column_vectorand its parity testWhy are the changes needed?
I am seeing this test and its parity test failing from time to time, and then fails
pyspark-sqlandpyspark-connect.It seems due to some log4j issue, e.g
https://github.com/zhengruifeng/spark/actions/runs/7459243602/job/20294868487
https://github.com/apache/spark/actions/runs/7460093200/job/20297508703
this PR simply attempt to retry it after failures
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