sunjincheng created FLINK-11972:
-----------------------------------
Summary: Fix `Command: start_kubernetes_if_not_ruunning failed`
error
Key: FLINK-11972
URL: https://issues.apache.org/jira/browse/FLINK-11972
Project: Flink
Issue Type: Bug
Components: Tests
Affects Versions: 1.8.0, 1.9.0
Reporter: sunjincheng
Attachments: image-2019-03-20-14-01-05-647.png,
image-2019-03-20-14-02-29-636.png
When I did the end-to-end test under Mac OS, I found the following two problems:
1. The verification returned for different `minikube status` is not enough for
the robustness. The strings returned by different versions of different
platforms are different. the following misjudgment is caused:
When the `Command: start_kubernetes_if_not_ruunning failed` error occurs, the
`minikube` has actually started successfully. The core reason is that there is
a bug in the `test_kubernetes_embedded_job.sh` script. The error message as
follows:
!image-2019-03-20-14-02-29-636.png!
So, I think we should improve the check logic of `minikube status`, What do
you think?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
