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

Flink Jira Bot updated FLINK-21564:
-----------------------------------
    Labels: auto-unassigned pull-request-available stale-assigned  (was: 
auto-unassigned pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issue is assigned but has not 
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a 
comment updating the community on your progress.  If this issue is waiting on 
feedback, please consider this a reminder to the committer/reviewer. Flink is a 
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone 
else may work on it.


> CommonTestUtils.waitUntilCondition could fail with condition meets before
> -------------------------------------------------------------------------
>
>                 Key: FLINK-21564
>                 URL: https://issues.apache.org/jira/browse/FLINK-21564
>             Project: Flink
>          Issue Type: Bug
>          Components: Tests
>            Reporter: Kezhu Wang
>            Assignee: Pedro Silva
>            Priority: Minor
>              Labels: auto-unassigned, pull-request-available, stale-assigned
>             Fix For: 1.15.0
>
>
> {code}
>     public static void waitUntilCondition(
>             SupplierWithException<Boolean, Exception> condition,
>             Deadline timeout,
>             long retryIntervalMillis,
>             String errorMsg)
>             throws Exception {
>         while (timeout.hasTimeLeft() && !condition.get()) {
>             final long timeLeft = Math.max(0, timeout.timeLeft().toMillis());
>             Thread.sleep(Math.min(retryIntervalMillis, timeLeft));
>         }
>         if (!timeout.hasTimeLeft()) {
>             throw new TimeoutException(errorMsg);
>         }
>     }
> {code}
> The timeout could run off between truth condition and last checking.
> Besides this, I also see time-out blocking condition in some tests, the 
> combination could be worse.
> Not a big issue, but worth to be aware of and solved.



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

Reply via email to