[SPARK-53374] Use release build in Apache Spark 4.1.0-preview1 testing
#220
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
force-pushed
the
SPARK-53374
branch
from
a91c3bd to
f750946
Compare
|
Apache Spark 4.1.0-preview1 test pipeline passed. The other failures are irrelevant. Merged to main. |
|
Thank you, @viirya ! |
|
Late LGTM. |
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?
This PR aims to use
releasebuild in Apache Spark4.1.0-preview1testing.Why are the changes needed?
Although we used
releasebuild in CI since SPARK-52085, we missed to enable it when we add a new test job in SPARK-52744.releasebuild in GitHub Action CI #136MacOSintegration test with Apache Spark4.1.0-preview1RC1 #210To be consistent, we need to use release build in CIs.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.