[SPARK-44468][BUILD] Add daily test GA task for branch3.5#42050
Closed
panbingkun wants to merge 1 commit into
Closed
[SPARK-44468][BUILD] Add daily test GA task for branch3.5#42050panbingkun wants to merge 1 commit into
panbingkun wants to merge 1 commit into
Conversation
LuciferYang
approved these changes
Jul 18, 2023
Contributor
|
cc @zhengruifeng @HyukjinKwon FYI |
Contributor
|
should we also make some changes in |
Member
|
yeah should also change:
cc @xuanyuanking who actually were going to fix soon :-). |
Member
|
That will be fixed in #42055 |
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?
The pr aims to add daily test GA task for branch3.5.
Why are the changes needed?
After the branch 3.5 is cut out from the master, we need a daily GA task to ensure the smooth release of version 3.5.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manually test.