mateczagany commented on PR #27061: URL: https://github.com/apache/flink/pull/27061#issuecomment-3350085736
Hi @davidradl , I will try to give some details. From my local machine it's quite rare to see this test fail, like the one in my other PR, but on my local machine, out of 10.000 test runs, about 100-200 fails without this fix. If you set the rootLogger level to WARN in `log4j2-test.properties`, you can see these errors: ``` Violation of main thread constraint detected: expected <Thread[#28,ForkJoinPool-1-worker-1,5,main]> but running in <Thread[#36,pool-2-thread-1,5,main]>. ``` And while writing this comment, I've also looked a bit deeper and realized that my solution was not really solving the core issue. I think this might be related to FLINK-38114, PR #26821 where not all tests were adjusted properly to fit the new behavior. I have pushed a new commit that updates the test so that all operations to the ExecutionGraph will run from the main thread. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
