davidradl commented on code in PR #27767:
URL: https://github.com/apache/flink/pull/27767#discussion_r2931468965
##########
flink-runtime/src/test/java/org/apache/flink/runtime/scheduler/SchedulerTestingUtils.java:
##########
@@ -340,6 +340,28 @@ public static void waitForCompletedCheckpoint(final
SchedulerNG scheduler) throw
RETRY_ATTEMPTS);
}
+ /**
+ * Waits until all task executions in the given ExecutionGraph reach
RUNNING state.
+ *
+ * @param executionGraph the ExecutionGraph to check
+ * @throws Exception if the condition is not met within the timeout period
Review Comment:
We have seen other tests with this sort of resolution. I think this is
reasonable. If we see timeouts then there will be another new underlying issue,
casing the vertices not to get to running. Is the timeout long enough for the
slow CIs?
--
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]
