Skip to content
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

[FLINK-10910][e2e] Hardened Kubernetes e2e test. #7507

Merged
merged 1 commit into from
Jan 30, 2019

Conversation

dawidwys
Copy link
Contributor

Added check if minikube is running. If it is not we try to start it couple of times. If we do not succeed we fail with a descriptive message.

What is the purpose of the change

This PR should harden kubernetes e2e test. It checks if kubernetes is running. If not it tries to start it. If it fails it exits with a descriptive error message.

Verifying this change

Run test_kubernetes_embedded_job.sh script. I've run ~100 times this test on travis, without a single failure (https://travis-ci.org/dawidwys/flink/builds/480346541). I also checked locally if it succeeds if minikube is not started.

@dawidwys
Copy link
Contributor Author

@aljoscha Could you maybe have a look at it?

@aljoscha aljoscha self-requested a review January 29, 2019 12:27
Copy link
Contributor

@aljoscha aljoscha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this looks good! I had one comment, but feel free to merge without addressing that.

@@ -37,10 +39,28 @@ function cleanup {
rm -rf ${OUTPUT_VOLUME}
}

function check_kubernetes_status {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm guessing these work because the return value of a bash function is implicitly the return value of the last executed command?

Maybe we can make that more explicit so that we don't accidentally break it in the future if someone adds another line after the last line. (This is also something I don't like that much about Scala ...)

Added check if minikube is running. If it is not we try to start it couple of times. If we do not succeed we fail with a descriptive message.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants