Relax timing for some socket tests a little bit. Hopefully this fixes the spurious hangs on Travis builds there.

1 files changed, 3 insertions, 3 deletions

diff --git a/tests/socket.test b/tests/socket.test
index dc3c04a..6579277 100644
--- a/tests/socket.test
+++ b/tests/socket.test
@@ -116,9 +116,9 @@ catch {socket 127.0.0.1 [randport]}
 set t2 [clock milliseconds]
 set lat2 [expr {($t2-$t1)*3}]
 
-# Use the maximum of the two latency calculations, but at least 100ms
+# Use the maximum of the two latency calculations, but at least 200ms
 set latency [expr {$lat1 > $lat2 ? $lat1 : $lat2}]
-set latency [expr {$latency > 100 ? $latency : 1000}]
+set latency [expr {$latency > 200 ? $latency : 200}]
 unset t1 t2 s1 s2 lat1 lat2 server
 
 # If remoteServerIP or remoteServerPort are not set, check in the environment
@@ -644,7 +644,7 @@ test socket_$af-2.11 {detecting new data} -constraints [list socket supported_$a
     vwait sock
     puts $s2 one
     flush $s2
-    after idle {set x 1}
+    after $latency {set x 1}; # Spurious failures in Travis CI, if we do [after idle]
     vwait x
     fconfigure $sock -blocking 0
     set result a:[gets $sock]