-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-28937][SPARK-28936][KUBERNETES] Reduce test flakyness #25765
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-28937][SPARK-28936][KUBERNETES] Reduce test flakyness #25765
Conversation
… of Spark K8s integration tests
…do a more complete env check
|
Test build #110490 has finished for PR 25765 at commit
|
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
Test build #110492 has finished for PR 25765 at commit
|
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
jenkins retest this please |
|
Test build #110527 has finished for PR 25765 at commit
|
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
test this please |
|
(i triggered this because i renamed the k8s prb job, and just want to be sure nothing breaks) |
|
Test build #110540 has finished for PR 25765 at commit
|
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #110549 has finished for PR 25765 at commit
|
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Jenkins retest this please |
|
Test build #110557 has finished for PR 25765 at commit
|
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
test this please |
|
(sorry for barging in again but i'm testing a small infra change on the ubuntu workers) ;) |
|
Test build #110571 has finished for PR 25765 at commit
|
|
It's 100% ok :) |
|
Kubernetes integration test starting |
awesome. i'm getting rid of those crappy, unrelated-to-the-build |
|
Kubernetes integration test status success |
aaaaaand those error messages are gone!
|
|
Awesome @shaneknapp :D |
| val SECRET_MOUNT_PATH = "/etc/secret" | ||
| val ENV_SECRET_KEY_1 = "username" | ||
| val ENV_SECRET_KEY_2 = "password" | ||
| val ENV_SECRET_KEY_1_CAP = ENV_SECRET_KEY_1.toUpperCase(Locale.ROOT) |
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.
Is this part of the change related, necessary?
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.
No, although I figured cleaning up hard coded strings while I was there would be good.
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
| .writingOutput(out) | ||
| .writingError(System.err) | ||
| .withTTY() | ||
| .usingListener(listener) |
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.
Cool I was looking for something like that in the past :)
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.
Rocking :)
|
If no one objects I plan to merge this tomorrow. |
|
Merged to master. |
What changes were proposed in this pull request?
Switch from using a Thread sleep for waiting for commands to finish to just waiting for the command to finish with a watcher & improve the error messages in the SecretsTestsSuite.
Why are the changes needed?
Currently some of the Spark Kubernetes tests have race conditions with command execution, and the frequent use of eventually makes debugging test failures difficult.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existing tests pass after removal of thread.sleep