[ 
https://issues.apache.org/jira/browse/FLINK-26702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508100#comment-17508100
 ] 

Biao Geng commented on FLINK-26702:
-----------------------------------

Hi [~mbalassi] you are not alone. I have also seen this failure in my openning 
PR's CI in my own github in the morning. I am not so sure why my CI is 
triggered. But I happened to set the build config of in my own CI to show more 
info for other issues and I got the full error messgae of this failure:
{quote}[INFO] Running 
org.apache.flink.kubernetes.operator.observer.JobObserverTest
2022-03-17 03:23:31,091 o.a.f.k.o.o.JobObserver [INFO ] [.] Getting job 
statuses for test-cluster
2022-03-17 03:23:31,091 o.a.f.k.o.o.JobObserver [INFO ] [.] Job statuses 
updated for test-cluster
2022-03-17 03:23:31,091 o.a.f.k.o.o.JobObserver [INFO ] [.] Getting job 
statuses for test-cluster
2022-03-17 03:23:31,091 o.a.f.k.o.o.JobObserver [INFO ] [.] Job statuses 
updated for test-cluster
2022-03-17 03:23:31,091 o.a.f.k.o.o.JobObserver [INFO ] [.] Getting job 
statuses for test-cluster
2022-03-17 03:23:31,091 o.a.f.k.o.o.JobObserver [INFO ] [.] Job statuses 
updated for test-cluster
2022-03-17 03:23:31,093 o.a.f.k.o.o.JobObserver [INFO ] [.] JobManager 
deployment test-cluster in namespace flink-operator-test exists but not ready, 
status DeploymentStatus(availableReplicas=1, collisionCount=null, 
conditions=[], observedGeneration=null, readyReplicas=null, replicas=1, 
unavailableReplicas=null, updatedReplicas=null, additionalProperties={})
2022-03-17 03:23:31,093 o.a.f.k.o.o.JobObserver [INFO ] [.] JobManager 
deployment test-cluster in namespace flink-operator-test exists but not ready, 
status DeploymentStatus(availableReplicas=1, collisionCount=null, 
conditions=[], observedGeneration=null, readyReplicas=null, replicas=1, 
unavailableReplicas=null, updatedReplicas=null, additionalProperties={})
2022-03-17 03:23:31,093 o.a.f.k.o.o.JobObserver [INFO ] [.] JobManager 
deployment test-cluster in namespace flink-operator-test port ready, waiting 
for the REST API...
2022-03-17 03:23:31,093 o.a.f.k.o.o.JobObserver [INFO ] [.] Getting job 
statuses for test-cluster
2022-03-17 03:23:31,093 o.a.f.k.o.o.JobObserver [INFO ] [.] Job statuses 
updated for test-cluster
2022-03-17 03:23:31,093 o.a.f.k.o.o.JobObserver [INFO ] [.] Getting job 
statuses for test-cluster
2022-03-17 03:23:31,093 o.a.f.k.o.o.JobObserver [INFO ] [.] Job statuses 
updated for test-cluster
Error: Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.039 s 
<<< FAILURE! - in org.apache.flink.kubernetes.operator.observer.JobObserverTest
Error: 
org.apache.flink.kubernetes.operator.observer.JobObserverTest.observeApplicationCluster
 Time elapsed: 0.013 s <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: <0> but was: <1>
at 
org.apache.flink.kubernetes.operator.observer.JobObserverTest.observeApplicationCluster(JobObserverTest.java:99)
{quote}
 

> Sporadic failures in JobObserverTest
> ------------------------------------
>
>                 Key: FLINK-26702
>                 URL: https://issues.apache.org/jira/browse/FLINK-26702
>             Project: Flink
>          Issue Type: Bug
>          Components: Kubernetes Operator
>            Reporter: Márton Balassi
>            Priority: Major
>
> I have occasionally observed the following failure during the regular build:
>  
> {code:java}
> mvn clean install
> ...
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.244 
> s - in org.apache.flink.kubernetes.operator.service.FlinkServiceTest
> [INFO] Running 
> org.apache.flink.kubernetes.operator.validation.DeploymentValidatorTest
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 
> s - in org.apache.flink.kubernetes.operator.validation.DeploymentValidatorTest
> [INFO] 
> [INFO] Results:
> [INFO] 
> [ERROR] Failures: 
> [ERROR]   JobObserverTest.observeApplicationCluster:99 expected: <0> but was: 
> <1>
> [INFO] 
> [ERROR] Tests run: 34, Failures: 1, Errors: 0, Skipped: 0
> [INFO] 
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Flink Kubernetes: .................................. SUCCESS [  4.223 
> s]
> [INFO] Flink Kubernetes Shaded ............................ SUCCESS [  5.097 
> s]
> [INFO] Flink Kubernetes Operator .......................... FAILURE [ 34.596 
> s]
> [INFO] Flink Kubernetes Webhook ........................... SKIPPED
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Total time: 44.065 s
> [INFO] Finished at: 2022-03-17T09:43:22+01:00
> [INFO] Final Memory: 160M/554M
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M4:test (default-test) 
> on project flink-kubernetes-operator: There are test failures.
> [ERROR] 
> [ERROR] Please refer to 
> /Users/mbalassi/git/apple/apache-flink-kubernetes-operator/flink-kubernetes-operator/target/surefire-reports
>  for the individual test results.
> [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> [ERROR] -> [Help 1]{code}
> I do not have a reliable way of reproducing this, however I have also seen CI 
> failures recently that could be do to this (unfortunately the log was 
> truncated):
> https://github.com/apache/flink-kubernetes-operator/runs/5582743074?check_suite_focus=true



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to