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-26882] Check the Kubernetes integration tests scalatyle #23792
[SPARK-26882] Check the Kubernetes integration tests scalatyle #23792
Conversation
The WIP part is to resolve any scala style issues that pop up during CI. |
Kubernetes integration test starting |
Kubernetes integration test status failure |
Test build #102365 has finished for PR 23792 at commit
|
@@ -29,6 +29,7 @@ ERRORS=$(echo -e "q\n" \ | |||
-Phive-thriftserver \ | |||
-Pspark-ganglia-lgpl \ | |||
-Pdocker-integration-tests \ | |||
-Pkubernetes-integration-tests \ |
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 recall the way this is setup right now, buildin the profile will try to execute the tests?
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 mean we aren't building the profile per-se, we're only evaluating scalastyle
test:scalastyle
on it, but let me double check locally.
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.
Running ./dev/scalastyle
after this change locally does not trigger the k8s integration tests
Hmm, I wonder how style errors were not triggered here? Maybe the PR builders don't use that script? I had to make a style change in |
@vanzin I think the PR builders do a different style check yeah, I'll dig into that as well and keep this as WIP. |
@vanzin Looking at Jenkins it looks like we depend on the scala-style-during-compile configuration now days for CI and the k8s integration tests have a skip flag turned on for that. |
Kubernetes integration test starting |
Kubernetes integration test status success |
Ok I think fixing this in CI is probably better done in a separate PR, I've created a follow up issue SPARK-26898 , I think someone who is more familiar with how the K8s integration build is set up will make more progress on that. |
Test build #102402 has finished for PR 23792 at commit
|
Merging to master. Although I really wish some build would fail if there was a style issue, preferably a PR build. |
What changes were proposed in this pull request?
Add the kubernetes integration tests to the scalastyle profiles.
How was this patch tested?
Run ./dev/scalastyle with a bad change manually
Follow on work
See SPARK-26898 to add scalastyle for k8s integration to the CI