[SPARK-54053] Use Swift 6.2 for all Linux CIs #255
Closed
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
commented
Oct 28, 2025
| docker run swift:6.1 uname -a | ||
| docker run -v $PWD:/spark -w /spark swift:6.1 swift build -c release | ||
| build-ubuntu-swift62: |
There was a problem hiding this comment.
This is merged into build-ubuntu-latest.
|
Could you review this PR, @peter-toth ? |
viirya
approved these changes
Oct 28, 2025
peter-toth
approved these changes
Oct 28, 2025
|
Thank you, @viirya and @peter-toth . Merged to main. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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?
This PR aims to use
Swift 6.2for all Linux CIs.Why are the changes needed?
To improve the CI stability on Linux environment by using the latest
Swift 6.2version.Does this PR introduce any user-facing change?
No, this is a CI change.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.