-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-37103][INFRA] Switch from Maven to SBT to build Spark on AppVeyor #34373
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
Conversation
| } | ||
|
|
||
| # ========================== Maven | ||
| # Push-Location $tools |
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.
I'll just comment out the instructions for installing Maven so that we can easily switch back to Maven after the StackOverflowError is resolved.
|
Test build #144561 has finished for PR 34373 at commit
|
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
HyukjinKwon
left a comment
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.
wow this is super nice. Thanks @sarutak
|
Merged to master!! |
|
Oops my mistake. I thought all build passed. Let me revert this one. |
Co-authored-by: Hyukjin Kwon <[email protected]>
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #144562 has finished for PR 34373 at commit
|
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #144563 has finished for PR 34373 at commit
|
|
Merged to master. |
What changes were proposed in this pull request?
This PR proposes to switch from Maven to SBT to build Spark on AppVeyor.
Why are the changes needed?
Recently, building Spark on AppVeyor almost always fails due to StackOverflowError at compile time.
We can't identify the reason so far but one workaround would be building with SBT.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
AppVeyor itself.