[MINOR][PYTHON][TESTS] Move test test_named_arguments_negative to test_arrow_python_udf#46544
Closed
zhengruifeng wants to merge 1 commit intoapache:masterfrom
Closed
[MINOR][PYTHON][TESTS] Move test test_named_arguments_negative to test_arrow_python_udf#46544zhengruifeng wants to merge 1 commit intoapache:masterfrom
test_named_arguments_negative to test_arrow_python_udf#46544zhengruifeng wants to merge 1 commit intoapache:masterfrom
Conversation
zhengruifeng
force-pushed
the
move_test_named_arguments_negative
branch
from
8b8c708 to
9b47396
Compare
HyukjinKwon
approved these changes
May 13, 2024
Contributor
Author
|
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
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?
Move test
test_named_arguments_negativetotest_arrow_python_udfWhy are the changes needed?
it seems was added in a wrong place, it only runs in Spark Connect, not Spark Classic.
After this PR, it will also be run in Spark Classic
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