Hi Shanliang,
On 20.2.2014 19:20, shanliang wrote:
Jaroslav,
The failed tests were:
1, 7, 8, 9
but the tests using this port (port2: 50235) were
1, 3, 4, 6, 7, 8, 9
and tests 2,4,6 were passed.
so I think that the problem might be that the port was not fully
released when a test was
Jaroslav,
The failed tests were:
1, 7, 8, 9
but the tests using this port (port2: 50235) were
1, 3, 4, 6, 7, 8, 9
and tests 2,4,6 were passed.
so I think that the problem might be that the port was not fully
released when a test was trying to use it, even the port was closed by
the pre
Looks good.
You have a commented out call to debugPortUsage(pa); which you can remove
before pushing.
Thanks,
/Staffan
On 20 feb 2014, at 15:21, Jaroslav Bachorik
wrote:
> Please, review this test fix.
>
> Issue : https://bugs.openjdk.java.net/browse/JDK-8035395
> Webrev: http://cr.openjdk.
Please, review this test fix.
Issue : https://bugs.openjdk.java.net/browse/JDK-8035395
Webrev: http://cr.openjdk.java.net/~jbachorik/8035395/webrev.00
Currently, the test is using two fixed ports to start JMX connector and
RMI registry when necessary. It can not deal with situations when the
p
