[ 
https://issues.apache.org/jira/browse/FLINK-22564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matthias updated FLINK-22564:
-----------------------------
    Description: 
-It appears that the k8s ITCases located in {{test_kubernetes_itcases.sh}} are 
not running (e.g. 
[here|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=17412&view=ms.vss-test-web.build-test-results-tab&runId=494592&resultId=100770&paneView=debug]
 and 
[here|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=17556&view=ms.vss-test-web.build-test-results-tab&runId=505566&resultId=100765&paneView=debug])
 due to {{ITCASE_KUBECONFIG}} not being available within the JVM.-

New Findings: The ITCases actually run as part of the e2e tests. But they do 
not seem to fail in case of a failure. {{Run Kubernetes IT test}} has passed 
[in this build 
#17556|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=17556&view=logs&j=c88eea3b-64a0-564d-0031-9fdcd7b8abee&t=ff888d9b-cd34-53cc-d90f-3e446d355529&l=2913]
 even though {{KubernetesStateHandleStoreITCase}} failed (see 
[here|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=17556&view=logs&j=c88eea3b-64a0-564d-0031-9fdcd7b8abee&t=ff888d9b-cd34-53cc-d90f-3e446d355529&l=2805]).

  was:
-It appears that the k8s ITCases located in {{test_kubernetes_itcases.sh}} are 
not running (e.g. 
[here|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=17412&view=ms.vss-test-web.build-test-results-tab&runId=494592&resultId=100770&paneView=debug]
 and 
[here|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=17556&view=ms.vss-test-web.build-test-results-tab&runId=505566&resultId=100765&paneView=debug])
 due to {{ITCASE_KUBECONFIG}} not being available within the JVM.-

New Findings: The ITCases actually run as part of the e2e tests. But they do 
not seem to fail in case of a failure. {{Run Kubernetes IT test}} has passed 
[in this build 
#17556](https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=17556&view=logs&j=c88eea3b-64a0-564d-0031-9fdcd7b8abee&t=ff888d9b-cd34-53cc-d90f-3e446d355529&l=2913]
 even though {{KubernetesStateHandleStoreITCase}} failed (see 
[here](https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=17556&view=logs&j=c88eea3b-64a0-564d-0031-9fdcd7b8abee&t=ff888d9b-cd34-53cc-d90f-3e446d355529&l=2805)).


> Kubernetes-related ITCases do not fail even in case of failure
> --------------------------------------------------------------
>
>                 Key: FLINK-22564
>                 URL: https://issues.apache.org/jira/browse/FLINK-22564
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / Kubernetes, Test Infrastructure
>    Affects Versions: 1.13.0, 1.12.3
>            Reporter: Matthias
>            Priority: Major
>              Labels: test-stability
>             Fix For: 1.13.1, 1.12.4
>
>
> -It appears that the k8s ITCases located in {{test_kubernetes_itcases.sh}} 
> are not running (e.g. 
> [here|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=17412&view=ms.vss-test-web.build-test-results-tab&runId=494592&resultId=100770&paneView=debug]
>  and 
> [here|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=17556&view=ms.vss-test-web.build-test-results-tab&runId=505566&resultId=100765&paneView=debug])
>  due to {{ITCASE_KUBECONFIG}} not being available within the JVM.-
> New Findings: The ITCases actually run as part of the e2e tests. But they do 
> not seem to fail in case of a failure. {{Run Kubernetes IT test}} has passed 
> [in this build 
> #17556|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=17556&view=logs&j=c88eea3b-64a0-564d-0031-9fdcd7b8abee&t=ff888d9b-cd34-53cc-d90f-3e446d355529&l=2913]
>  even though {{KubernetesStateHandleStoreITCase}} failed (see 
> [here|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=17556&view=logs&j=c88eea3b-64a0-564d-0031-9fdcd7b8abee&t=ff888d9b-cd34-53cc-d90f-3e446d355529&l=2805]).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to