xiaoHoly commented on pull request #14076:
URL: https://github.com/apache/flink/pull/14076#issuecomment-731058522
@tillrohrmann ,Maybe I found the reason for the instability. It depends on
when the thread A calling the await() method acquires the lock of the lock
object in the jvm lock poo
xiaoHoly commented on pull request #14076:
URL: https://github.com/apache/flink/pull/14076#issuecomment-731061272
To facilitate the discussion, I will post the code below：
method of Thead A!
public void await() throws InterruptedException {
synchronized (lock) {
xiaoHoly commented on pull request #14076:
URL: https://github.com/apache/flink/pull/14076#issuecomment-727752237
HI,@tillrohrmann .PTAL
This is an automated message from the Apache Git Service.
To respond to the message, pl
xiaoHoly commented on pull request #14076:
URL: https://github.com/apache/flink/pull/14076#issuecomment-727750065
> @xiaoHoly It will trigger the test atomically when you pushing a new
commit. Usually there is no need to trigger the test manually. Besides, you can
use command `@flinkbot ru
xiaoHoly commented on pull request #14076:
URL: https://github.com/apache/flink/pull/14076#issuecomment-727747755
@flinkbot run azure re-run the last Azure build
This is an automated message from the Apache Git Service.
To re
xiaoHoly commented on pull request #14076:
URL: https://github.com/apache/flink/pull/14076#issuecomment-727747601
@flinkbot run travis re-run the last Travis build
This is an automated message from the Apache Git Service.
To
