Thanks Alan. Yes, I think it's reasonable to set a much larger timeout.
The actual delay experienced (annoying as it is) will still be only two
seconds.
I'll go ahead with that.
Michael.
On 03/12/2019 11:08, Alan Bateman wrote:
On 03/12/2019 09:59, Michael McMahon wrote:
:
8234823:
On 03/12/2019 09:59, Michael McMahon wrote:
:
8234823: java/net/Socket/Timeouts.java testcase testTimedConnect2()
fails on Windows 10
http://cr.openjdk.java.net/~michaelm/8234823/webrev.1/
For this one, it should be okay to increase the timeout to a much larger
timeout if you want. For
Could I get the following two trivial test case fixes reviewed please?
They are both caused by a recent configuration change to Windows 10
where socket connect
requests are attempted four times, at 500ms intervals, on connection
refused errors,
which means that such connects will take around 2
