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

Yi Zhang updated FLINK-39311:
-----------------------------
    Description: 
Several tests in DispatcherApplicationTest are flaky, e.g.

Error: 02:53:58 02:53:58.665 [ERROR] Errors: 
Error: 02:53:58 02:53:58.665 [ERROR] 
DispatcherApplicationTest.testApplicationStatusChange_ThrowsIfDuplicateTerminalStatus:212
 » Timeout


The issue can be reproduced locally by running the test repeatedly until 
failure. The logs from failed runs contain error messages like:


9553 [ForkJoinPool.commonPool-worker-19] WARN  
org.apache.flink.runtime.rpc.MainThreadValidatorUtil [] - Violation of main 
thread constraint detected: expected <null> but running in 
<Thread[ForkJoinPool.commonPool-worker-19,5,main]>.
java.lang.Exception: Violation of main thread constraint detected: expected 
<null> but running in <Thread[ForkJoinPool.commonPool-worker-19,5,main]>.
at 
org.apache.flink.runtime.rpc.MainThreadValidatorUtil.isRunningInExpectedThread(MainThreadValidatorUtil.java:73)
at 
org.apache.flink.runtime.rpc.RpcEndpoint.validateRunsInMainThread(RpcEndpoint.java:463)
at 
org.apache.flink.runtime.rpc.RpcEndpoint$MainThreadExecutor.assertRunningInMainThread(RpcEndpoint.java:581)
at 
org.apache.flink.runtime.dispatcher.cleanup.DefaultApplicationResourceCleaner.cleanupAsync(DefaultApplicationResourceCleaner.java:141)
at 
org.apache.flink.runtime.dispatcher.Dispatcher.removeApplication(Dispatcher.java:1125)
at 
org.apache.flink.runtime.dispatcher.Dispatcher.lambda$notifyApplicationStatusChange$12(Dispatcher.java:984)
at 
java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1072)
at 
java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:479)

  was:
Several tests in DispatcherApplicationTest are flaky, e.g.


Error: 02:53:58 02:53:58.665 [ERROR] Errors: 
Error: 02:53:58 02:53:58.665 [ERROR] 
DispatcherApplicationTest.testApplicationStatusChange_ThrowsIfDuplicateTerminalStatus:212
 » Timeout


> Flaky tests in DispatcherApplicationTest
> ----------------------------------------
>
>                 Key: FLINK-39311
>                 URL: https://issues.apache.org/jira/browse/FLINK-39311
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Yi Zhang
>            Priority: Major
>
> Several tests in DispatcherApplicationTest are flaky, e.g.
> Error: 02:53:58 02:53:58.665 [ERROR] Errors: 
> Error: 02:53:58 02:53:58.665 [ERROR] 
> DispatcherApplicationTest.testApplicationStatusChange_ThrowsIfDuplicateTerminalStatus:212
>  » Timeout
> The issue can be reproduced locally by running the test repeatedly until 
> failure. The logs from failed runs contain error messages like:
> 9553 [ForkJoinPool.commonPool-worker-19] WARN  
> org.apache.flink.runtime.rpc.MainThreadValidatorUtil [] - Violation of main 
> thread constraint detected: expected <null> but running in 
> <Thread[ForkJoinPool.commonPool-worker-19,5,main]>.
> java.lang.Exception: Violation of main thread constraint detected: expected 
> <null> but running in <Thread[ForkJoinPool.commonPool-worker-19,5,main]>.
> at 
> org.apache.flink.runtime.rpc.MainThreadValidatorUtil.isRunningInExpectedThread(MainThreadValidatorUtil.java:73)
> at 
> org.apache.flink.runtime.rpc.RpcEndpoint.validateRunsInMainThread(RpcEndpoint.java:463)
> at 
> org.apache.flink.runtime.rpc.RpcEndpoint$MainThreadExecutor.assertRunningInMainThread(RpcEndpoint.java:581)
> at 
> org.apache.flink.runtime.dispatcher.cleanup.DefaultApplicationResourceCleaner.cleanupAsync(DefaultApplicationResourceCleaner.java:141)
> at 
> org.apache.flink.runtime.dispatcher.Dispatcher.removeApplication(Dispatcher.java:1125)
> at 
> org.apache.flink.runtime.dispatcher.Dispatcher.lambda$notifyApplicationStatusChange$12(Dispatcher.java:984)
> at 
> java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1072)
> at 
> java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:479)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to