-
Notifications
You must be signed in to change notification settings - Fork 28.6k
[SPARK-47127][INFRA] Update SKIP_SPARK_RELEASE_VERSIONS
in Maven CIs
#45212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SPARK-47127][INFRA] Update SKIP_SPARK_RELEASE_VERSIONS
in Maven CIs
#45212
Conversation
If the following PR fails, I'll file a JIRA issue and make this PR cc @LuciferYang and @HyukjinKwon |
.github/workflows/build_maven.yml
Outdated
@@ -33,5 +33,5 @@ jobs: | |||
with: | |||
envs: >- | |||
{ | |||
"SKIP_SPARK_RELEASE_VERSIONS": "3.3.4,3.4.2,3.5.0" | |||
"SKIP_SPARK_RELEASE_VERSIONS": "3.4.2,3.5.0,3.5.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
3.3.4
is removed and 3.5.1
is added. For now, 3.5.0 is not removed yet.
Thank you, @HyukjinKwon . |
SKIP_SPARK_RELEASE_VERSIONS
in Maven CIs
Merged to master. |
hmm... If ivy 2.5.2 is not upgraded,I think Spark 3.5.1 can be tested and passed using maven .... |
### What changes were proposed in this pull request? This PR aims to update `SKIP_SPARK_RELEASE_VERSIONS` in Maven CIs in order to prevent failures. ### Why are the changes needed? - To skip newly released Apache Spark 3.5.1 - To remove deleted Apache Spark 3.3.4 and 3.5.0. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? This should be tested after merging. ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#45212 from dongjoon-hyun/SKIP_SPARK_RELEASE_VERSIONS. Authored-by: Dongjoon Hyun <dhyun@apple.com> Signed-off-by: Dongjoon Hyun <dhyun@apple.com>
What changes were proposed in this pull request?
This PR aims to update
SKIP_SPARK_RELEASE_VERSIONS
in Maven CIs in order to prevent failures.Why are the changes needed?
Does this PR introduce any user-facing change?
No.
How was this patch tested?
This should be tested after merging.
Was this patch authored or co-authored using generative AI tooling?
No.