From: Henri Sara <hesara@vaadin.com>
Date: Mon, 4 Aug 2014 05:23:01 +0000 (+0300)
Subject: Increase TB3 socket timeout to 30 min (#14352)
X-Git-Tag: 7.3.0.rc1~11^2~77
X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=295f116b91789bc0ff5422e54f2df4e59eb53294;p=vaadin-framework.git

Increase TB3 socket timeout to 30 min (#14352)

This increases the timeout from 15 to 30 minutes to avoid
occasional timeouts at times of test cluster congestion.
The timeout was originally reduced for #14298.

Change-Id: I59e8ad892356c94954d0d20884319de653704ca4
---

diff --git a/uitest/src/com/vaadin/tests/tb3/TB3Runner.java b/uitest/src/com/vaadin/tests/tb3/TB3Runner.java
index 4241b9fa6c..0d540644bf 100644
--- a/uitest/src/com/vaadin/tests/tb3/TB3Runner.java
+++ b/uitest/src/com/vaadin/tests/tb3/TB3Runner.java
@@ -57,10 +57,10 @@ public class TB3Runner extends BlockJUnit4ClassRunner {
 
     /**
      * Socket timeout for HTTP connections to the grid hub. The connection is
-     * closed after 15 minutes of inactivity to avoid builds hanging for up to
+     * closed after 30 minutes of inactivity to avoid builds hanging for up to
      * three hours per connection if the test client crashes/hangs.
      */
-    private static final int SOCKET_TIMEOUT = 15 * 60 * 1000;
+    private static final int SOCKET_TIMEOUT = 30 * 60 * 1000;
 
     /**
      * This is the total limit of actual JUnit test instances run in parallel