[SPARK-51628][INFRA] Clean up the assembly module before maven testing in maven daily test#50387
Closed
LuciferYang wants to merge 4 commits intoapache:masterfrom
Closed
Conversation
assembly module before maven testingassembly module before maven testing
assembly module before maven testingassembly module before maven testing in maven daily test
assembly module before maven testing in maven daily testassembly module before maven testing in maven daily test
Contributor
Author
zhengruifeng
approved these changes
Mar 27, 2025
Contributor
Author
|
Merged into master. Thanks @dongjoon-hyun @zhengruifeng |
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?
During the Maven daily test process, this pr has added cleanup work for the
assemblymodule beforemvn test(except for theconnectmodule, as some tests in theconnect-client-jvmmodule strongly depend on the completion of theassemblymodule build) to prevent the issue described in SPARK-51600 (#50385) from being unverifiable in the Maven daily test.Why are the changes needed?
Reduce the dependency of Maven daily test on the completion of the
assemblymodule build.Does this PR introduce any user-facing change?
No, just for maven daily test.
How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?
No