You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yang Wang (Jira)" <ji...@apache.org> on 2019/12/23 08:25:00 UTC
[jira] [Commented] (FLINK-15354) Start and stop minikube only in
kubernetes related e2e tests
[ https://issues.apache.org/jira/browse/FLINK-15354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002149#comment-17002149 ]
Yang Wang commented on FLINK-15354:
-----------------------------------
[~trohrmann] Please assign this ticket to me. After [FLINK-15360|https://issues.apache.org/jira/browse/FLINK-15360] fixed, i will attached a PR to move the minikube start/stop only in kubernetes related tests.
> Start and stop minikube only in kubernetes related e2e tests
> ------------------------------------------------------------
>
> Key: FLINK-15354
> URL: https://issues.apache.org/jira/browse/FLINK-15354
> Project: Flink
> Issue Type: Bug
> Reporter: Yang Wang
> Priority: Major
>
> Currently, we start minikube in {{nightly.sh for every e2e test}}, and it will never be stopped. It is unnecessary and will occupy some resources on travis. I think the minikube should only be started in the kubernetes related test(\{{test_kubernetes_embedded_job.sh}}) and need to be stopped once the test finished.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)