-
-
Notifications
You must be signed in to change notification settings - Fork 316
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CryptoTests_0 FAILED in x86-32_windows, x86-64_windows, arm_linux and solaris platforms #4336
Comments
@judovana Summary:
Windows: (we currently do not run on win)
|
I have created PR, which should fix ConfigurationTests on Windows: |
These PRs should fix remaining issues on Windows: |
thanks kindly @zzambers ! |
I re-tested this: x86-64_windows: OK arm_linux: OK Seems like there are no more windows issues after Cryptotest fixes. I think this issue can be closed. (I cannot close it myself) |
I had assumed you already addressed these issues, thanks for confirming with Grinder @zzambers, closing this now. |
There is still a failure on 32bit windows (deep history). |
Problem is SignatureTests timeout (240s) on win32, with stacktrace such as (just to make sure, information is not lost):
See also: I went through several results, all timeout, while performing BigInteger arithmetic (so not on blocking method like e.g. reading from random). Probably BigInteger arithmetic is just slow on some platforms.. :/ |
Will also exclude on Solaris platforms until they can be fixed there. (See #4518 (comment) and #4518 (comment)). |
I think reason of slowness on 32-bit Intel (and possibly other platforms) may be due to absence of intrinsics on these platforms. Method from stacktrace and some other BigInteger methods are marked but intrinsics seem to be only available for x86_64 (64-bit): which could explain this... (as platforms without intrinsics would fall back to java code, which is slower) I have made PR to increase timeout for SignatureTests: |
On arm_linux appears that the error is intermittent, one of the 31 testcases are timing out:
Deep history shows that it 'sometimes' passes: Possible cause for intermittency is described in: eclipse-openj9/openj9#16712 (comment) |
2 failures, 2 errors on Windows 32bit builds (and 2 failures on x86-64_windows see Test_openjdk11_hs_extended.functional_x86-64_windows/330
2 errors on arm_linux
Test Info
Test Name: CryptoTests_0
Test Duration: 24 min 35 sec
Machine: test-ibmcloud-win2012r2-x64-1
TRSS link for the test output: https://trss.adoptium.net/output/test?id=63e8120aed0b30773bfa2876
Build Info
Build Name: Test_openjdk11_hs_extended.functional_x86-32_windows
Jenkins Build start time: Feb 11 2023, 12:52 pm
Jenkins Build URL: https://ci.adoptopenjdk.net/job/Test_openjdk11_hs_extended.functional_x86-32_windows/323/
TRSS link for the build: https://trss.adoptium.net/allTestsInfo?buildId=63e8110aed0b30773bfa233f
Java Version
openjdk version "11.0.18" 2023-01-17
OpenJDK Runtime Environment Temurin-11.0.19+1 (build 11.0.18+1)
OpenJDK Client VM Temurin-11.0.19+1 (build 11.0.18+1, mixed mode)
Rerun in Grinder
Console:
The text was updated successfully, but these errors were encountered: