Increase test timeouts in TCPChannelClientTest

This test fails on slow runners when TCPChannelClient has not
yet finished communication, but the test thread times out checking
that mock methods are called.

Bug: webrtc:9955
Change-Id: Ia91ada6b01ca1bab48afa57fe76aedd08770a641
Reviewed-on: https://webrtc-review.googlesource.com/c/111383
Commit-Queue: Artem Titarenko <artit@webrtc.org>
Reviewed-by: Sami Kalliomäki <sakal@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#25751}
This commit is contained in:
Artem Titarenko
2018-11-20 15:59:24 +01:00
committed by Commit Bot
parent 00dfe932a7
commit 42d2e4bbb1

View File

@ -38,10 +38,10 @@ public class TCPChannelClientTest {
* How long we wait before trying to connect to the server. Note: was
* previously only 10, which was too short (tests were flaky).
*/
private static final int SERVER_WAIT = 100;
private static final int CONNECT_TIMEOUT = 100;
private static final int SEND_TIMEOUT = 100;
private static final int DISCONNECT_TIMEOUT = 100;
private static final int SERVER_WAIT = 300;
private static final int CONNECT_TIMEOUT = 1000;
private static final int SEND_TIMEOUT = 1000;
private static final int DISCONNECT_TIMEOUT = 1000;
private static final int TERMINATION_TIMEOUT = 1000;
private static final String TEST_MESSAGE_SERVER = "Hello, Server!";
private static final String TEST_MESSAGE_CLIENT = "Hello, Client!";