RFR 8085575_8130657, misc fixes for a few of java.net intermittent failures
felix.yang at oracle.com
Mon Sep 26 13:47:38 UTC 2016
thanks for the information. That is why I stated it is the nature of such scenario. Some of such scenarios look like not avoidable.
> On 26 Sep 2016, at 5:57 PM, Xuelei Fan <xuelei.fan at oracle.com> wrote:
> Just FYI.
> The intermittent failures look like similar to some anti-free-port using issues. In the current testing environment, for the InheritHandle test case, this anti-free-port using issue may looks like:
> 1. InheritHandle creates a server socket on a free port, and gets the port (PORT-A). (line 60-61)
> 2. InheritHandle close the server socket. (line 87)
> 3. Another test (TEST-B) creates a server socket on a free port. PORT-A may be used by the TEST-B.
> 4. InheritHandle create new server socket on PORT-A (line 88), it is expected to fail as PORT-A has been used by TEST-B.
> The InheritHandle.java may run into intermittent failure unless it is run single alone.
> On 9/26/2016 3:56 PM, Felix Yang wrote:
>> Hi there,
>> please review following patch to a few of java.net tests.
>> Add retry for java/net/Socket/InheritHandle.java. Though it may be
>> unable to resolve all BindException ( I suppose it is the nature of such
>> close-reuse scenarios), it will be helpful to avoid failures from
>> asynchronized close, which has been observed especially on Windows. Also
>> some misc changes on other two tests.
More information about the net-dev