LocalHTTPDManagerTest: extend timeout to 60 seconds
If the job is successful, it should finish without coming closes to the timeout. Extending the timeout will make it take longer to fail, but since the job is flaky, and the related code is rarely touched, it seems worth it.
This commit is contained in:
parent
69b845c34f
commit
474bbdfdbd
@ -50,7 +50,7 @@ public class LocalHTTPDManagerTest {
|
||||
startLatch.countDown();
|
||||
}
|
||||
}).start();
|
||||
assertTrue(startLatch.await(30, TimeUnit.SECONDS));
|
||||
assertTrue(startLatch.await(60, TimeUnit.SECONDS));
|
||||
assertTrue(Utils.isServerSocketInUse(port));
|
||||
assertTrue(Utils.canConnectToSocket(host, port));
|
||||
|
||||
@ -69,6 +69,6 @@ public class LocalHTTPDManagerTest {
|
||||
stopLatch.countDown();
|
||||
}
|
||||
}).start();
|
||||
assertTrue(stopLatch.await(10, TimeUnit.SECONDS));
|
||||
assertTrue(stopLatch.await(60, TimeUnit.SECONDS));
|
||||
}
|
||||
}
|
||||
|
Loading…
x
Reference in New Issue
Block a user