On 08/01/16 10:56, Jaroslav Bachorik wrote:
On 7.1.2016 17:32, Daniel Fuchs wrote:
On 06/01/16 12:23, Jaroslav Bachorik wrote:
On 6.1.2016 12:19, David Holmes wrote:
On 6/01/2016 8:21 PM, Jaroslav Bachorik wrote:
Please, review the following test change
Issue : https://bugs.openjdk.java.net/browse/JDK-8145919
Webrev: http://cr.openjdk.java.net/~jbachorik/8145919/webrev.00
On AArch64 machines running multiple test rounds involving SSL
connections in rapid succession leads to error during SSL handshake.
I can't see how this could be CPU specific. This is more likely an OS
issue or an issue with the network hardware/environment of the test
machines.
Test is failing on AArch64 linux - various machines. I did more than 20
runs on the test infrastructure and the test is consistently failing on
AArch64, no matter which machine takes up the job. I don't have a
separate standalone AArch64 hardware to cross-check. Therefore I went
down the path of the most obvious solution ...
Looks good to me.
RmiSslBootstrapTest.sh:
Is jdk.testlibrary.* and /jdk/testlibrary still needed? It seems the
test now only uses jdk.test.lib (unless jdk.testlibrary has classes
in the unnamed package?)
Correct, thanks. We can remove reference to the jdk specific test library.
Updated webrev: http://cr.openjdk.java.net/~jbachorik/8145919/webrev.01
Looks good.
-- daniel
-JB-
cheers,
-- daniel
-JB-
David
The fix is attempting to workaround this by inserting an arbitrary
delay
between the test rounds on AArch64 platform. The fix has been verified
and makes the test pass reliably.
Thanks,
-JB-
