Repository navigation
[SPARK-47377][PYTHON][CONNECT][TESTS][FOLLOWUP] Factor out more tests from SparkConnectSQLTestCase - #45533
Closed
zhengruifeng wants to merge 1 commit into
Closed
[SPARK-47377][PYTHON][CONNECT][TESTS][FOLLOWUP] Factor out more tests from SparkConnectSQLTestCase#45533zhengruifeng wants to merge 1 commit into
SparkConnectSQLTestCase#45533zhengruifeng wants to merge 1 commit into
Conversation
zhengruifeng
force-pushed
the
continue_break_basic
branch
from
March 15, 2024 12:37
99bbb9b to
69da09a
Compare
Member
|
LGTM when CI passed, thanks! I triggered rerun cause the failed tests seem to be irrelevant to the PR |
xinrong-meng
approved these changes
Mar 15, 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?
It is a fallowup of #45497 , and factor out more tests from
SparkConnectSQLTestCaseIt should also be the laster PR for this test :)
Why are the changes needed?
for testing parallelism
Does this PR introduce any user-facing change?
no
How was this patch tested?
ci
Was this patch authored or co-authored using generative AI tooling?
no