-
Notifications
You must be signed in to change notification settings - Fork 729
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
openJcePlusTests_0_FAILED timed out at runCurveMixTest #19200
Comments
Succeeded 10/10 on cent8x86-rtp-rt8-1 @jasonkatonica fyi |
The failures aren't in the 0.44 builds but I assume openJcePlus is the same. Added to the 0.44 milestone for now. |
Also seen at JDK11 x86-64_linux( |
The timeout is increased to 2hrs (see PR) |
Just for the record, it seems that sles15x86-rtp-rt2-1.fyre.ibm.com is slow. The test passed and took ~74 mins on this machine. The test usually takes ~20mins on the other machines. For details, see link. I will close this issue. Please reopen if the problem occurs again. |
Seen at JDK21 x86-64_linux(
|
@llxia another re-occurrence after increasing the timeout. |
@jasonkatonica do you have any suggestions? Or should I increase the timeout again? |
We have not seen these tests take over 2 hours typically on the machines we have worked with. Additionally there is a pattern emerging here that the test Given failing logs I dont believe that increasing the timeout would be helpful at this point and we will need to investigate further. |
This issue can be closed since work has been done to improve the multi-thread tests in OpenJCEPlus using IBM/OpenJCEPlus#207 |
Issue Number: 19200 |
Failure link
From an internal build(
sles15x86-rtp-rt2-1
):Rerun in Grinder - Change TARGET to run only the failed test targets.
Optional info
Failure output (captured from console output)
50x internal grinder - #19200 (comment)
The text was updated successfully, but these errors were encountered: