[MINOR][TESTS][DOCS] Use fully-qualified class name in docker integration test #30448
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
dongjoon-hyun
changed the title
dongjoon-hyun
approved these changes
Nov 20, 2020
There was a problem hiding this comment.
+1, LGTM. Thanks, @huaxingao .
Merged to master for Apache Spark 3.1.0.
cc @maropu
dongjoon-hyun
changed the title
|
BTW, @huaxingao . I revised the PR title from |
|
Thank you! @dongjoon-hyun |
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
Test build #131433 has finished for PR 30448 at commit
|
|
Thanks for the update, @huaxingao late LGTM |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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?
change
to
Why are the changes needed?
We only want to start v1
xxxIntegrationSuite, not the newly addedv2.xxxIntegrationSuite.Does this PR introduce any user-facing change?
No
How was this patch tested?
Manually checked