-
Notifications
You must be signed in to change notification settings - Fork 29.1k
[SPARK-38597][K8S][INFRA] Enable Spark on K8S integration tests #37244
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
3f282c9 to
0023bd3
Compare
|
Thank you for your patience and reviving this, @Yikun . |
.github/workflows/build_and_test.yml
Outdated
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 believe we should enable k8s test always instead of this. core module changes will affect many scheduling tests too.
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.
FYI, historically, log4j2 change also causes K8s integration test failure due to log4j2.properties file changes.
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.
OK, I will change this soon.
0023bd3 to
9190afb
Compare
dongjoon-hyun
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.
+1, LGTM. Thank you, @Yikun . The SQL UT failure is irrelevant to this GitHub Action.
Merged to master for Apache Spark 3.4.
|
@dongjoon-hyun Thanks! I will monitor it closely for the next few days. |
|
Thank you for your consistent participation, @Yikun . |

What changes were proposed in this pull request?
Enable Spark on K8S integration tests in Github Action based on minikube:
The K8S IT will always triggered in user fork repo and
apache/sparkmerged commits to master branchThis PR does NOT contains Volcano related test due to limited resource of github action.
minikube installation is allowed by Apache Infra: INFRA-23000
Why setting driver 0.5 cpu, executor 0.2 cpu?
Exiting due to RSRC_OVER_ALLOC_MEM: Requested memory allocation 7168MB is more than your system limit 6947MB.), but this is not integer multiple of 1024, so I just set this to 6144 for better resource statistic.Time cost info:
Why are the changes needed?
This will also improve the efficiency of K8S development and guarantee the quality of spark on K8S and spark docker image in some level.
Does this PR introduce any user-facing change?
No, dev only.
How was this patch tested?
CI passed
Closes #35830