tillrohrmann commented on a change in pull request #18569:
URL: https://github.com/apache/flink/pull/18569#discussion_r795750059
##########
File path:
flink-kubernetes/src/test/java/org/apache/flink/kubernetes/highavailability/KubernetesHighAvailabilityRecoverFromSavepointITCase.java
##########
@@ -101,12 +102,14 @@ public void setup() throws Exception {
@Test
public void testRecoverFromSavepoint() throws Exception {
final JobGraph jobGraph = createJobGraph();
- clusterClient.submitJob(jobGraph).get(TIMEOUT, TimeUnit.MILLISECONDS);
+ clusterClient
+ .submitJob(jobGraph)
+ .get(TestingUtils.infiniteTime().toMilliseconds(),
TimeUnit.MILLISECONDS);
Review comment:
Yes and no. With an infinite timeout, we would have failed and created a
stack trace. This stack trace would have shown the deadlock right away. Now it
took me a bit of digging to find the problem. Therefore, I decided to change
this test to use very long timeouts.
--
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: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
